@wayai/cli@0.3.195
WayAI CLI — sync hub configuration between local files and the platform
AI Security Review
scanned 27d ago · by lpm-firewall-aiThe configurable API destination can receive the WayAI session token without an allowlist, a concrete conditional credential exposure that warrants a warning. No source evidence establishes covert theft or an automatic install-time attack.
Decision evidence
public snapshot- The CLI accepts a caller-supplied `--api-url` without a visible destination restriction.
- Browser login obtains a WayAI access token and persists the selected API URL for later commands.
- The API client builds requests from that configured URL and sends its access token as a bearer credential.
- The configured URL is also used by the explicit update command; no automatic lifecycle hook is declared.
- The default API endpoint is `https://api.wayai.pro`, and browser authentication uses the WayAI AuthKit domain.
- The agent skill paths are WayAI-owned integration locations, and `wayai init` only prints an instruction to install the skill.
- The package has no preinstall, install, or postinstall script in its manifest.
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.195.
See all versions of @wayai/cli for other recorded verdicts.
- Review the evidence and your use of @wayai/cli@0.3.195 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.