@wayai/cli@0.3.218
WayAI CLI — sync hub configuration between local files and the platform
AI Security Review
scanned 19d ago · by lpm-firewall-aiThe bundle supports a warning because ordinary CLI use can extend the existing WayAI skill into Claude's project configuration without a separate confirmation. The manifest has no install hook, and the flagged login behavior defaults to WayAI's service or uses an endpoint explicitly supplied by the caller; the other scanner labels do not establish a concrete attack.
Decision evidence
public snapshot- The manifest exposes a CLI entry point and has no install lifecycle hook.
- The bundle recognizes WayAI skills in project-level Claude, OpenCode, and agent directories.
- On a non-help command, the CLI checks for a project skill in the agent directory and can link it into Claude's skill directory when that destination is absent.
- The link is limited to the existing WayAI skill; help commands are excluded.
- Login uses WayAI's default API endpoint, while an alternate endpoint must be supplied with the login option.
- The skill link is limited to a project-local destination and does not establish broad agent configuration changes or credential disclosure.
- The manifest's scripts are build, development, type-check, and test commands; none is an install hook.
Source & flagged code
7 flaggedFindings
Affected versions and remediation
This report applies to @wayai/cli@0.3.218.
See all versions of @wayai/cli for other recorded verdicts.
- Review the evidence and your use of @wayai/cli@0.3.218 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.