@wayai/cli@0.3.278
WayAI CLI — sync hub configuration between local files and the platform
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe source enables runtime error reporting to Sentry by default and attaches command and account identifiers, while the inspected package provides no disclosure of that collection. Secret masking and an opt-out reduce the risk, so this warrants a warning rather than a malicious verdict.
Decision evidence
public snapshot- The CLI initializes Sentry automatically on invocation, unless it is running a background refresh.
- For an installed package, Sentry reporting is enabled by default; the source provides a disable environment variable but no telemetry disclosure in the inspected package.
- Sentry events include the command, Node version, OS platform and architecture, and are sent to the hard-coded Sentry endpoint.
- Sentry associates events with a 16-character hash of a WayAI token or the subject identifier from an OAuth token.
- The Sentry hook masks secrets in error messages and shortens home-directory paths, which limits—but does not remove—the identifying data collected.
- The manifest has no install, preinstall or postinstall lifecycle hook.
- The Sentry endpoint is a Sentry collector, and the CLI’s API credential flows otherwise target WayAI or the relevant service.
- The source masks secrets in reported error messages and hashes WayAI tokens before using them as Sentry user IDs.
Source & flagged code
8 flaggedFindings
Affected versions and remediation
This report applies to @wayai/cli@0.3.278.
See all versions of @wayai/cli for other recorded verdicts.
- Review the evidence and your use of @wayai/cli@0.3.278 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.