@wayai/cli@0.3.193
WayAI CLI — sync hub configuration between local files and the platform
AI Security Review
scanned 27d ago · by lpm-firewall-aiThe inspected source supports ordinary CLI behavior, with update installation available only through an explicit command. The static signals do not establish malicious behavior.
Decision evidence
public snapshot- The manifest has no npm install lifecycle hook; it exposes the CLI through `dist/index.js`.
- The flagged agent location names WayAI skill paths in harness directories; automatic refresh fetches skill text and caches its version.
- Login uses the default WayAI API unless the user supplies `--api-url`; the API client sends the token to that selected endpoint.
- The CLI’s npm installation command runs through the explicit `wayai 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.193.
See all versions of @wayai/cli for other recorded verdicts.
- Review the evidence and your use of @wayai/cli@0.3.193 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.