@wayai/cli@0.3.217
WayAI CLI — sync hub configuration between local files and the platform
AI Security Review
scanned 21d ago · by lpm-firewall-aiThe manifest has no install hook, and source inspection found no hidden payload execution or credential redirection. The flagged network, dynamic import, and process behavior aligns with CLI login, version checks, and explicit commands.
Decision evidence
public snapshot- package.json exposes a CLI binary and lists build and development scripts, with no install lifecycle hook.
- Browser login uses an authorization-code flow with PKCE; the API defaults to WayAI, or accepts an explicit --api-url, and returned tokens are stored locally.
- Report requests use the configured API URL and require an interactive terminal outside CI.
- The required agent integration location defines project skill paths; nearby code reads skill files for versions, and refresh fetches version metadata.
Source & flagged code
8 flaggedFindings
Affected versions and remediation
This report applies to @wayai/cli@0.3.217.
See all versions of @wayai/cli for other recorded verdicts.
- Review the evidence and your use of @wayai/cli@0.3.217 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.