@wayai/cli@0.3.222
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 hook, authenticated requests use the default WayAI API or an explicitly selected API URL, and npm installation is confined to the explicit update command. Agent skill changes are local and depend on an existing skill or an explicit install command.
Decision evidence
public snapshot- package.json defines only build, development, typecheck, and test scripts; it has no install lifecycle hook.
- Login uses the configured AuthKit service and defaults to api.wayai.pro; changing the API URL requires an explicit --api-url argument.
- Authenticated requests send a bearer token to the configured API URL. The source does not establish a hidden, unrelated default recipient.
- The .claude skill link is created only when a WayAI skill already exists under .agents and the Claude skill is absent; the repair runs during CLI invocation.
- Admin skill installation is a separate command that requires authentication and writes returned files into project harness skill directories.
- The npm install operation is confined to the explicit wayai update command.
Source & flagged code
7 flaggedFindings
Affected versions and remediation
This report applies to @wayai/cli@0.3.222.
See all versions of @wayai/cli for other recorded verdicts.
- Review the evidence and your use of @wayai/cli@0.3.222 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.