@wayai/cli@0.3.263
WayAI CLI — sync hub configuration between local files and the platform
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe main risk is default runtime error telemetry to Sentry without disclosure in the package’s user-facing text. The source masks some exception details and offers an opt-out, so this warrants a warning rather than a malicious verdict.
Decision evidence
public snapshot- When the CLI runs, it initializes Sentry using a hard-coded DSN for installed packages unless `WAYAI_TELEMETRY_DISABLED=1` is set.
- CLI errors that pass `shouldReportToSentry` are sent through `captureException`; the report includes exception details and stack traces, with some masking and path redaction.
- The Sentry DSN points to `o4510669417807872.ingest.us.sentry.io`.
- The manifest identifies this as the WayAI CLI and routes its `wayai` executable to `dist/index.js`.
- The OpenAI key use found is for speech synthesis and sends the key to OpenAI’s own `api.openai.com` endpoint.
- The package manifest has no install lifecycle scripts.
Source & flagged code
10 flaggedFindings
Affected versions and remediation
This report applies to @wayai/cli@0.3.263.
See all versions of @wayai/cli for other recorded verdicts.
- Review the evidence and your use of @wayai/cli@0.3.263 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.