@wayai/cli@0.3.178
WayAI CLI — sync hub configuration between local files and the platform
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe source shows a guarded automatic agent-extension migration during CLI use, but no lifecycle hook, broad configuration rewrite, payload execution, or exfiltration. This fits a non-blocking agent extension lifecycle risk.
Decision evidence
public snapshot- The package exposes a WayAI command-line executable.
- The executable detects an existing WayAI skill under the project agent directory and a missing Claude skill directory.
- For qualifying commands it creates a project-local Claude skill symlink pointing to that agent skill.
- This repair is reached automatically for non-help CLI invocations rather than through a dedicated setup command.
- No npm preinstall, install, or postinstall hook was present in the inspected package metadata.
- The mutation is guarded by an existing project-local WayAI skill and does not replace a non-symlink destination.
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.178.
See all versions of @wayai/cli for other recorded verdicts.
- Review the evidence and your use of @wayai/cli@0.3.178 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.