@wayai/cli@0.3.211
WayAI CLI — sync hub configuration between local files and the platform
AI Security Review
scanned 23d ago · by lpm-firewall-aiThe package has no install hook, and the suspicious credential flow is an OAuth exchange for the WayAI service rather than a transfer of a prompted provider credential. The agent integration repairs a first-party skill link, while package installation is not shown performing the flagged behavior.
Decision evidence
public snapshot- package.json declares the CLI entrypoint and has no install lifecycle hook.
- The login flow uses browser OAuth, exchanges an authorization code with AuthKit, and stores returned tokens for WayAI access.
- The default API endpoint is api.wayai.pro; the AuthKit domain is configured for this login flow.
- The agent integration targets WayAI skill directories; its helper repairs a Claude skill link only when the WayAI skill already exists under .agents.
- The updater is reached through the explicit 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.211.
See all versions of @wayai/cli for other recorded verdicts.
- Review the evidence and your use of @wayai/cli@0.3.211 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.