@wayai/cli@0.3.206
WayAI CLI — sync hub configuration between local files and the platform
AI Security Review
scanned 24d ago · by lpm-firewall-aiThe CLI permits an unrestricted API URL and forwards the WayAI bearer token to it, creating a conditional credential exposure risk. The default endpoint is package-aligned and the override is caller-selected, so this warrants a warning rather than a block.
Decision evidence
public snapshot- Login accepts an arbitrary endpoint through `--api-url`, with no destination check in the parser.
- Token validation sends a bearer token to the selected endpoint’s `/api/auth/me` route.
- Authenticated commands load a saved API URL and token before making requests.
- The package has no install lifecycle hook; the flagged agent integration constants name WayAI skill files and directories.
- The default API endpoint is the package’s WayAI service, and the endpoint override is explicitly supplied when invoking login.
- The agent integration excerpt only defines skill installation paths; it does not itself mutate agent configuration.
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.206.
See all versions of @wayai/cli for other recorded verdicts.
- Review the evidence and your use of @wayai/cli@0.3.206 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.