@wayai/cli@0.3.223
WayAI CLI — sync hub configuration between local files and the platform
AI Security Review
scanned 17d ago · by lpm-firewall-aiStatic hints prompted review, but inspected source shows no install hook and no concrete malicious behavior. The update and local skill-link actions are attributable to CLI invocation, while login defaults to the package’s WayAI service and stores the selected endpoint.
Decision evidence
public snapshot- package.json exposes dist/index.js as the CLI entry point and declares no install lifecycle hook.
- The CLI’s default API endpoint is api.wayai.pro; an alternate endpoint is selected with the explicit --api-url argument and saved for that login.
- The agent integration hint covers local skill directories; the related helper creates a .claude skill link to the WayAI skill under .agents when a CLI command runs.
- The updater is a named CLI command that checks for and installs a newer @wayai/cli release; background version refresh is disabled in CI or by the user’s environment settings.
- Inspected credential handling stores OAuth tokens through the token store and records the API URL; the inspected login path does not redirect credentials to an unrelated fixed gateway.
- The flagged dynamic require is bundle support code, and the inspected payload decoding parses a token field for Sentry identity reporting; no hidden code execution was found in those excerpts.
Source & flagged code
7 flaggedFindings
Affected versions and remediation
This report applies to @wayai/cli@0.3.223.
See all versions of @wayai/cli for other recorded verdicts.
- Review the evidence and your use of @wayai/cli@0.3.223 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.