@wayai/cli@0.3.196
WayAI CLI — sync hub configuration between local files and the platform
AI Security Review
scanned 27d ago · by lpm-firewall-aiThe inspected source shows no install lifecycle hook and the suspicious signals correspond to normal, user-invoked CLI authentication and updating. The cited agent integration location identifies product skill paths but does not show an install-time mutation or attack.
Decision evidence
public snapshot- package.json defines no install lifecycle hook; its scripts are build, development, typecheck, and tests.
- The bundle’s login flow uses a loopback callback and exchanges the authorization code with the configured AuthKit service.
- The required agent integration location defines WayAI skill paths for supported agent directories; this alone does not establish an attack.
- The update command checks and installs a newer release only when the user invokes it.
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.196.
See all versions of @wayai/cli for other recorded verdicts.
- Review the evidence and your use of @wayai/cli@0.3.196 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.