@wayai/cli@0.3.198
WayAI CLI — sync hub configuration between local files and the platform
AI Security Review
scanned 27d ago · by lpm-firewall-aiThe CLI automatically exposes an already-installed WayAI skill to Claude by creating a project-local symlink on ordinary command use. This is a concrete but limited agent integration capability, so warn without blocking publication.
Decision evidence
public snapshot- On normal CLI commands, the bundle checks for an existing WayAI skill under `.agents` and may create a corresponding `.claude` skill symlink.
- The link repair runs from the foreground command path, while help and version commands are excluded.
- Login accepts an explicitly supplied API URL and otherwise uses the WayAI API; the inspected code does not establish credential theft.
- The manifest has no install lifecycle hooks; its executable is the CLI entry point.
- The link operation is limited to exposing an already-present WayAI skill and leaves an existing Claude skill in place.
- The inspected update and version-refresh paths update the CLI or version caches; no hidden payload execution was established.
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.198.
See all versions of @wayai/cli for other recorded verdicts.
- Review the evidence and your use of @wayai/cli@0.3.198 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.