registry / @wayai/cli / 0.3.151
@wayai/cli@0.3.151
WayAI CLI — sync hub configuration between local files and the platform
AI Security Review
scanned 27d ago · by lpm-firewall-aiThe manifest has no npm install hook, and the flagged package-manager command belongs to the explicit self-update command. The agent integration only repairs a link for the package's own skill, so the inspected source does not establish an attack surface.
Static reason
One or more suspicious static signals were detected.
Trigger
Running the `wayai` command can invoke the link repair; installing the CLI update is triggered by the explicit `wayai update` command.
Impact
These actions do not establish malicious behavior: the skill change is limited to the package's own named skill, and the package installation is an explicit user-invoked update.
Mechanism
The repair links an existing `.agents/skills/wayai` directory into `.claude/skills/wayai` when its skill file exists and the destination file is missing. The update command installs a newer release of this same CLI after checking its version.
AI rationale
The manifest has no npm install hook, and the flagged package-manager command belongs to the explicit self-update command. The agent integration only repairs a link for the package's own skill, so the inspected source does not establish an attack surface.
Evidence
.claude/skills/wayai@wayai/cli
Decision evidence
public snapshotAI called this Clean at 93.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest exposes the bundled file as the `wayai` CLI and has no install lifecycle hook.
- The package install command appears in the explicit update flow, which checks the published version and installs the latest `@wayai/cli` only when an update is available.
- The agent-related paths are limited to named `wayai` and `wayai-admin` skill files in `.claude`, `.opencode`, and `.agents`.
- On ordinary CLI commands, the bundle may repair a missing `.claude` link to an existing `.agents/skills/wayai` skill; version refresh runs in a separate child process with explicit refresh flags.
Evidence against
- No inspected source showed a package install hook, broad agent configuration mutation, credential exfiltration, or a hidden install chain.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
4 flaggeddist/index.jsView file
14617});
L14618: import { execFileSync } from "child_process";
L14619: import * as fs2 from "fs";
High
51while (cursor < text.length) {
L52: while (cursor < text.length && !isBase64UrlChar(text[cursor])) cursor++;
L53: const headerStart = cursor;
...
L236: "use strict";
L237: CREDENTIAL_KEY_RE = /token|secret|credential|password|passwd|api[_-]?key|authorization|private[_-]?key|session[_-]?id|cookie|jwt/i;
L238: NUMERIC_CREDENTIAL_KEY_RE = /(?:password|passwd|pin|token|secret|credential|api[_-]?key|authorization|private[_-]?key|session[_-]?id|cookie|jwt)$/i;
...
L249: [/\bway_[A-Za-z0-9_-]{8,}/g, "way_[REDACTED]"],
L250: // wst_ single-use WebSocket tickets (same opaque base64url format).
L251: [/\bwst_[A-Za-z0-9_-]{8,}/g, "wst_[REDACTED]"],
...
L366: try {
L367: const __dirname2 = dirname(fileURLToPath(import.meta.url));
L368: const pkg2 = JSON.parse(readFileSync(join(__dirname2, "..", "
High
Sandbox Evasion Gated Capability
Source gates dangerous network, credential, or execution behavior behind CI, host, platform, time, or geo fingerprint checks.
dist/index.jsView on unpkg · L5115766package = @wayai/cli; repositoryIdentity = platform; dependency = @napi-rs/keyring
L15766: try {
L15767: const mod = await import("@napi-rs/keyring");
L15768: const Entry = mod.Entry;
Findings
5 High3 Medium4 Low
HighChild Processdist/index.js
HighShell
HighSandbox Evasion Gated Capabilitydist/index.js
HighCopied Package Dependency Bridgedist/index.js
HighRuntime Package Installdist/index.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @wayai/cli@0.3.151.
See all versions of @wayai/cli for other recorded verdicts.
- Review the evidence and your use of @wayai/cli@0.3.151 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.