@wayai/cli@0.3.239
WayAI CLI — sync hub configuration between local files and the platform
AI Security Review
scanned 15d ago · by lpm-firewall-aiSource inspection found no install-time attack or hidden payload execution. The credential path follows the caller-selected API URL, and the runtime npm install is available through the explicit update command.
Decision evidence
public snapshot- package.json exposes dist/index.js and lists only build, development, typecheck, and test scripts. The inspected prepared dependency manifests and runtime files contain ordinary validation, keyring, and Sentry/OpenTelemetry code; no preinstall, install, or postinstall hook was found.
- Login defaults to the WayAI API. A different API URL is read from the explicit --api-url option, and login stores the selected URL with the resulting credential.
- API requests use the configured API URL and attach the access token as a bearer credential.
- The npm global install command is reached through the explicit wayai update command.
- Sentry reporting uses a fixed Sentry endpoint; WayAI-format token identifiers are hashed before being set as the Sentry user.
Source & flagged code
8 flaggedFindings
Affected versions and remediation
This report applies to @wayai/cli@0.3.239.
See all versions of @wayai/cli for other recorded verdicts.
- Review the evidence and your use of @wayai/cli@0.3.239 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.