@wayai/cli@0.3.201
WayAI CLI — sync hub configuration between local files and the platform
AI Security Review
scanned 24d ago · by lpm-firewall-aiThe manifest exposes a CLI without an install hook, and the reviewed network and update behaviors are consistent with explicit CLI functionality. Scanner flags alone do not establish a malicious loader or credential attack in the inspected source.
Decision evidence
public snapshot- package.json exposes a CLI and has no install lifecycle hook.
- The bundle's agent paths identify WayAI-owned skill files in known harness directories; the reviewed location is path configuration, not a broad agent-control write.
- Skill version refresh fetches a skill document and caches its version; no code execution is shown in this flow.
- The update command's npm operations are inside the explicit update command.
- The default API host is the package's WayAI service.
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.201.
See all versions of @wayai/cli for other recorded verdicts.
- Review the evidence and your use of @wayai/cli@0.3.201 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.