@wayai/cli@0.3.203
WayAI CLI — sync hub configuration between local files and the platform
AI Security Review
scanned 24d ago · by lpm-firewall-aiThe manifest has no install lifecycle hooks, and the inspected credential flow is initiated by an explicit login command with a user-selectable API endpoint. The scanner’s agent hint is a set of skill path constants, not evidence of an attack.
Decision evidence
public snapshot- The manifest exposes a CLI entrypoint and defines no install lifecycle hooks.
- The flagged agent-integration location names skill directories and filenames; it does not itself write agent configuration.
- Login uses the default API endpoint unless the user explicitly supplies --api-url, and persists the selected endpoint with tokens after login.
- OAuth tokens are stored through the token store after the browser login flow.
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.203.
See all versions of @wayai/cli for other recorded verdicts.
- Review the evidence and your use of @wayai/cli@0.3.203 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.