@wayai/cli@0.3.221
WayAI CLI — sync hub configuration between local files and the platform
AI Security Review
scanned 18d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and the flagged runtime actions are explicit CLI operations or use the WayAI API by default. The token destination can be changed with caller-supplied --api-url, while agent skill writes require an explicit authenticated command; the inspected source does not establish a hidden gateway or unconsented agent mutation.
Decision evidence
public snapshot- The manifest exposes dist/index.js as the CLI and lists no npm lifecycle scripts.
- The default API is https://api.wayai.pro. A caller may supply --api-url; token login prompts for a token, validates it at that URL, then stores the token and URL.
- The flagged harness paths are skill directories. The authenticated skill installer runs through an explicit admin command and writes the requested skill into those directories.
- The npm self-update runs through the explicit wayai update command; no install hook triggers it.
Source & flagged code
7 flaggedFindings
Affected versions and remediation
This report applies to @wayai/cli@0.3.221.
See all versions of @wayai/cli for other recorded verdicts.
- Review the evidence and your use of @wayai/cli@0.3.221 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.