@wayai/cli@0.3.216
WayAI CLI — sync hub configuration between local files and the platform
AI Security Review
scanned 22d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and the inspected login flow validates credentials against the selected API URL, defaulting to the WayAI API. The CLI’s project-level skill link is a concrete first-party agent integration capability, so this merits a warning rather than a block.
Decision evidence
public snapshot- package.json lists build, development, typecheck, and test scripts; it has no npm install lifecycle hook.
- The explicit login flow sends a supplied token to the selected API URL for validation; the default API URL is api.wayai.pro.
- The bundle identifies .claude, .opencode, and .agents as skill directories and uses SKILL.md to locate the WayAI skill.
- A non-help CLI command checks the project root for the skill link; when the source skill exists and the Claude Code skill is absent, it can create a .claude skill symlink to the existing .agents skill.
- The inspected login path does not support the scanner’s claim of credential redirection to an unrelated fixed gateway.
- The agent configuration change is scoped to exposing the existing WayAI skill to Claude Code and runs from a CLI command.
Source & flagged code
8 flaggedFindings
Affected versions and remediation
This report applies to @wayai/cli@0.3.216.
See all versions of @wayai/cli for other recorded verdicts.
- Review the evidence and your use of @wayai/cli@0.3.216 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.