@wayai/cli@0.3.185
WayAI CLI — sync hub configuration between local files and the platform
AI Security Review
scanned 1mo ago · by lpm-firewall-aiInspected source supports a behavior-specific warning for first-party agent extension setup, not a malware block. The scanner's hidden-loader and credential-theft labels were not substantiated by the inspected execution and authentication paths.
Decision evidence
public snapshot- package.json has no npm install lifecycle hooks or runtime self-dependency.
- The bundle targets WayAI skills in .claude, .opencode, and .agents.
- Ordinary non-help CLI commands can automatically link an existing WayAI skill into Claude's skill directory.
- The explicit admin skill install command authenticates to the configured platform and writes downloaded files into harness skill directories.
- Background skill refresh caches version metadata; installing updated skill content requires a separate command.
- No concrete hidden payload execution or covert credential export was established from inspected source.
- Skill linking requires an existing WayAI skill and preserves existing valid skill files.
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.185.
See all versions of @wayai/cli for other recorded verdicts.
- Review the evidence and your use of @wayai/cli@0.3.185 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.