@wayai/cli@0.3.265
WayAI CLI — sync hub configuration between local files and the platform
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe package performs runtime Sentry reporting by default and exposes only an opt-out in the inspected source, with no disclosure found in the package manifest. This is suspicious telemetry; the flagged OpenAI key flow and update command are consistent with explicit audio synthesis and user-invoked updating.
Decision evidence
public snapshot- Installed CLI commands initialize Sentry telemetry by default; WAYAI_TELEMETRY_DISABLED=1 disables it, and SENTRY_DSN can override the destination.
- Telemetry includes command, Node version, OS platform, and architecture; captured exceptions can include stack frames and error messages.
- The package embeds a Sentry endpoint at o4510669417807872.ingest.us.sentry.io.
- The manifest identifies this as a WayAI CLI and declares no install, preinstall, or postinstall hook.
- The OpenAI key is read for audio synthesis and passed to the OpenAI audio API client.
- The npm update command is a user-invoked CLI command.
Source & flagged code
10 flaggedFindings
Affected versions and remediation
This report applies to @wayai/cli@0.3.265.
See all versions of @wayai/cli for other recorded verdicts.
- Review the evidence and your use of @wayai/cli@0.3.265 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.