@wayai/cli@0.3.233
WayAI CLI — sync hub configuration between local files and the platform
AI Security Review
scanned 15d ago · by lpm-firewall-aiThe manifest has no install hook, and inspection of the reachable CLI source found no hidden payload execution or credential redirection. The flagged dependency files are Sentry/OpenTelemetry SDK modules; the CLI disables Sentry default integrations and tracing, while its login and upload paths follow explicit destination checks.
Decision evidence
public snapshot- package.json points the CLI executable to dist/index.js and lists build, development, type-check, and test scripts; it has no install lifecycle hook.
- Browser login uses PKCE with the AuthKit issuer. API-token login validates the entered token against the selected API URL, and successful login stores tokens locally.
- Sentry reporting has a disable flag, zero trace sampling, and default integrations disabled. The CLI hashes WayAI tokens for user association, uses the JWT subject for OAuth sessions, and masks secrets in event text.
- The attachment upload path checks the server-provided target against the expected data-proxy origin and path before sending file contents.
- The flagged dependency files are part of the declared Sentry SDK and its OpenTelemetry instrumentation; the CLI config does not enable Sentry default integrations.
- Installed CLI runs error telemetry to a fixed Sentry endpoint unless disabled; OAuth error reports can include the JWT subject as a user identifier.
Source & flagged code
8 flaggedFindings
Affected versions and remediation
This report applies to @wayai/cli@0.3.233.
See all versions of @wayai/cli for other recorded verdicts.
- Review the evidence and your use of @wayai/cli@0.3.233 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.