@wayai/cli@0.3.209
WayAI CLI — sync hub configuration between local files and the platform
AI Security Review
scanned 24d ago · by lpm-firewall-aiSource inspection found no install-time action, credential disclosure to an unrelated recipient, or active payload execution. The runtime package installation is limited to the user-invoked update command, and the indicated agent paths refer to the package's own skill.
Decision evidence
public snapshot- package.json exposes dist/index.js as the CLI entry point and defines no install lifecycle hook.
- The indicated agent integration location sets paths for the package's own WayAI skill; it does not itself install or modify an agent configuration.
- Browser login exchanges its authorization code with the configured AuthKit token endpoint; the default API is WayAI's service.
- The API URL can be supplied with the explicit --api-url option, and otherwise defaults to api.wayai.pro.
- The update command installs a newer release only when the user runs the update command.
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.209.
See all versions of @wayai/cli for other recorded verdicts.
- Review the evidence and your use of @wayai/cli@0.3.209 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.