@wayai/cli@0.3.205
WayAI CLI — sync hub configuration between local files and the platform
AI Security Review
scanned 24d ago · by lpm-firewall-aiThe source confirms that an operator-supplied API URL is persisted and receives bearer-authenticated requests, so conditional credential exposure warrants a warning. The default is package-aligned and the override is caller-supplied, with no evidence of covert forwarding or install-hook behavior.
Decision evidence
public snapshot- The manifest exposes a CLI and lists no install lifecycle hook.
- The bundled CLI accepts an arbitrary value for `--api-url` without validating its destination.
- Login saves that API URL for later use.
- Authenticated requests use the configured API URL and attach the access token as a bearer credential.
- The bundle names `.claude`, `.opencode`, and `.agents` as skill installation locations; this alone does not establish harmful agent configuration behavior.
- The default API endpoint is the package's WayAI service.
- The custom endpoint requires the caller to supply `--api-url` during login; no hidden redirection was identified.
- The manifest contains no preinstall, install, or postinstall hook.
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.205.
See all versions of @wayai/cli for other recorded verdicts.
- Review the evidence and your use of @wayai/cli@0.3.205 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.