@wayai/cli@0.3.202
WayAI CLI — sync hub configuration between local files and the platform
AI Security Review
scanned 24d ago · by lpm-firewall-aiThe manifest has no install hooks, and the inspected bundle behavior is consistent with an interactive CLI and its update checks. Scanner signals did not establish an active attack surface in the inspected source.
Decision evidence
public snapshot- package.json exposes the bundle as a CLI entrypoint and declares no install lifecycle hooks.
- The referenced agent integration constants identify WayAI skill files and destinations under supported harness directories.
- Background version refresh runs only when explicitly scheduled, and requested cache refreshes are selected through internal flags.
- The update command checks and installs a newer release only when the user invokes the update command.
- The scanner's dynamic loading, shell, network, credential-redirection, and obfuscated-loader signals do not establish malicious behavior in the inspected source.
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.202.
See all versions of @wayai/cli for other recorded verdicts.
- Review the evidence and your use of @wayai/cli@0.3.202 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.