@wayai/cli@0.3.246
WayAI CLI — sync hub configuration between local files and the platform
AI Security Review
scanned 10d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook. Source inspection traced the scanner’s package-install, child-process, credential, and dynamic-loading indicators to user-invoked CLI behavior, WayAI authentication, ordinary Sentry reporting, and bundled SDK code; no concrete attack chain was found.
Decision evidence
public snapshot- package.json lists build, development, typecheck, and test scripts, with no npm install lifecycle hook.
- The CLI validates credentials against its configured API URL, and API requests use that same configured URL.
- The required Sentry dependency paths contain Sentry or OpenTelemetry integrations, constants, and SDK exports.
- The CLI’s Sentry reporting can be disabled; its event handler masks credential-like values, while its user context is a token hash or OAuth subject.
Source & flagged code
8 flaggedFindings
Affected versions and remediation
This report applies to @wayai/cli@0.3.246.
See all versions of @wayai/cli for other recorded verdicts.
- Review the evidence and your use of @wayai/cli@0.3.246 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.