@wayai/cli@0.3.255
WayAI CLI — sync hub configuration between local files and the platform
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe bundle automatically reports runtime errors and account-derived identifiers to Sentry, with no disclosure found in the inspected package. The opt-out and secret masking reduce the risk, so this is suspicious telemetry rather than a clear malicious attack.
Decision evidence
public snapshot- Installed runs initialize Sentry with a hard-coded Sentry DSN unless telemetry is disabled by environment variable.
- Every foreground invocation initializes Sentry, including ordinary CLI commands.
- Sentry events are tagged with the command, Node version, operating system platform, and architecture.
- The package sets a Sentry user ID from a truncated hash of a WayAI token or the subject claim of a JWT.
- The normal authenticated command path passes the access token to that Sentry identity setter.
- Unhandled command errors are sent to Sentry and the client is flushed before exit.
- Telemetry can be disabled with WAYAI_TELEMETRY_DISABLED=1.
- The Sentry hook masks secrets in messages and breadcrumbs and replaces the home directory in stack paths.
- The manifest has no install, preinstall, or postinstall lifecycle hook; its stated purpose is syncing WayAI hub configuration.
Source & flagged code
10 flaggedFindings
Affected versions and remediation
This report applies to @wayai/cli@0.3.255.
See all versions of @wayai/cli for other recorded verdicts.
- Review the evidence and your use of @wayai/cli@0.3.255 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.