@wayai/cli@0.3.204
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 existing session token can be forwarded to an unrestricted configured endpoint, which is a concrete credential-exposure risk. The default destination is package-aligned, and the reviewed source does not establish covert exfiltration or install-time execution.
Decision evidence
public snapshot- The login command accepts a caller-supplied API URL and stores it in configuration without an apparent destination restriction.
- The CLI sends its stored access token in authenticated requests to the configured API URL, so a non-WayAI endpoint can receive that token.
- The package exposes a CLI entrypoint, and the inspected manifest defines no install lifecycle hook.
- The default API endpoint is api.wayai.pro; the inspected login flow stores tokens in the OS keyring.
- The package's automatic skill cache refresh reads metadata from a WayAI-owned GitHub repository; the cited agent skill paths are product-specific.
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.204.
See all versions of @wayai/cli for other recorded verdicts.
- Review the evidence and your use of @wayai/cli@0.3.204 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.