@wayai/cli@0.3.273
WayAI CLI — sync hub configuration between local files and the platform
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe source shows default runtime error reporting to Sentry, including a user identifier, without disclosure in the package manifest; an opt-out is available. The flagged OpenAI credential path is ordinary user-invoked TTS that sends the key directly to OpenAI, so the finding supports a telemetry warning rather than a malicious verdict.
Decision evidence
public snapshot- The CLI entry point initializes Sentry automatically; its default configuration uses a hardcoded Sentry DSN and offers an environment-variable opt-out.
- Unexpected foreground errors are captured and reported to Sentry.
- When WayAI authentication succeeds, the code attaches a hashed token identifier or JWT subject as the Sentry user ID.
- The manifest describes the CLI and declares no telemetry disclosure.
- The OpenAI key is used by an audio synthesis feature that sends it directly to api.openai.com.
- The Sentry setup masks secret-like text and removes the home-directory prefix from exception stack paths.
- The manifest has no install lifecycle script.
Source & flagged code
8 flaggedFindings
Affected versions and remediation
This report applies to @wayai/cli@0.3.273.
See all versions of @wayai/cli for other recorded verdicts.
- Review the evidence and your use of @wayai/cli@0.3.273 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.