@wayai/cli@0.3.254
WayAI CLI — sync hub configuration between local files and the platform
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe source initializes Sentry for installed foreground runs and captures reportable errors, with only an environment-variable opt-out and no clear disclosure in the reviewed package metadata. The credential and shell findings otherwise align with explicit CLI features: the OpenAI key goes to OpenAI for audio synthesis, and package installation has no lifecycle hook.
Decision evidence
public snapshot- The manifest describes a WayAI CLI and declares no install lifecycle scripts.
- Installed foreground runs initialize Sentry unless WAYAI_TELEMETRY_DISABLED=1; the default DSN points to o4510669417807872.ingest.us.sentry.io.
- The foreground error handler sends reportable errors to Sentry.
- The Sentry hook masks secrets in string-valued event extras and replaces the home directory in stack filenames.
- OPENAI_API_KEY is used for audio synthesis and sent to api.openai.com.
- The package is a CLI for syncing hub configuration with WayAI.
- The OpenAI key flow is tied to the audio synthesis feature and its own service endpoint.
- The Sentry path is error reporting; the reviewed code does not show it collecting credentials or unrelated files.
Source & flagged code
8 flaggedFindings
Affected versions and remediation
This report applies to @wayai/cli@0.3.254.
See all versions of @wayai/cli for other recorded verdicts.
- Review the evidence and your use of @wayai/cli@0.3.254 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.