@wayai/cli@0.3.179
WayAI CLI — sync hub configuration between local files and the platform
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe package does not use an npm install hook, but running the CLI can mutate first-party agent skill directories, including an authenticated download into Claude, OpenCode, and agents folders. That is guarded product setup rather than a covert install-time control-surface hijack.
Decision evidence
public snapshot- package.json exposes the wayai bin and only build, dev, typecheck, and test scripts, with no install lifecycle hook.
- Any wayai command other than help or version can create .claude/skills/wayai as a directory symlink to an existing .agents/skills/wayai skill.
- The authenticated wayai admin skill install command writes API-returned skill files into .claude, .opencode, and .agents skill directories.
- Skill linking and install run only after a user invokes the CLI, not during npm install or import.
- The automatic link is created only when the WayAI skill already exists under .agents and is missing under .claude.
- Downloaded skill paths are rejected unless each segment is a short safe filename.
Source & flagged code
7 flaggedManifest-reachable source sends a prompted API credential to a fixed unofficial gateway and persists the redirection.
dist/index.jsView on unpkgFindings
Affected versions and remediation
This report applies to @wayai/cli@0.3.179.
See all versions of @wayai/cli for other recorded verdicts.
- Review the evidence and your use of @wayai/cli@0.3.179 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.