@wayai/cli@0.3.182
WayAI CLI — sync hub configuration between local files and the platform
AI Security Review
scanned 1mo ago · by lpm-firewall-aiInspected source supports a guarded agent extension capability rather than malware. The supplied policy calls for a warning for first-party package-owned agent setup, while the absence of install hooks and concrete attack behavior does not support blocking.
Decision evidence
public snapshot- package.json has no npm install lifecycle hooks or runtime self-dependency.
- The flagged code identifies WayAI skill locations under .claude, .opencode, and .agents.
- Ordinary CLI commands can automatically link an existing WayAI skill into Claude's skill directory, preserving existing skill files and non-symbolic entries.
- The explicit admin skill install command authenticates to the configured platform and writes downloaded skill files into agent skill directories.
- Downloaded file names pass a relative-path safety check before writing.
- The integration is limited to package-owned skills and CLI activation; no confirmed malicious install-time mutation was established.
- Background version checks cache versions and suggest explicit update commands rather than automatically replacing installed skills.
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.182.
See all versions of @wayai/cli for other recorded verdicts.
- Review the evidence and your use of @wayai/cli@0.3.182 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.