@wayai/cli@0.3.169
WayAI CLI — sync hub configuration between local files and the platform
AI Security Review
scanned 27d ago · by lpm-firewall-aiInspected source supports a clean verdict: installation does not trigger package code, and the agent skill setup is an explicit CLI action using the WayAI API. Static signals for process execution and networking correspond to CLI self-update and version checks; no malicious behavior was established.
Decision evidence
public snapshot- The manifest identifies a WayAI CLI for syncing hub configuration and exposes dist/index.js as its command entrypoint.
- The manifest has no install lifecycle hook; its scripts are build, development, typecheck, and test tasks.
- The referenced agent integration targets the WayAI and WayAI Admin skill locations under .claude, .opencode, and .agents.
- Admin skill installation runs as a CLI command, uses authenticated API access, and writes returned files into harness skill directories.
- The background check only reports that an admin skill update is available and directs the user to run the install command.
- The CLI's self-update command checks and installs a newer @wayai/cli release when explicitly run.
Source & flagged code
4 flaggedSource gates dangerous network, credential, or execution behavior behind CI, host, platform, time, or geo fingerprint checks.
dist/index.jsView on unpkg · L51Findings
Affected versions and remediation
This report applies to @wayai/cli@0.3.169.
See all versions of @wayai/cli for other recorded verdicts.
- Review the evidence and your use of @wayai/cli@0.3.169 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.