registry / @expo/agent-cli / 1.0.19
@expo/agent-cli@1.0.19
Agent-native CLI on top of the Expo CLI family
AI Security Review
scanned 19d ago · by lpm-firewall-aiThe package has no install-time activation, and the flagged agent configuration behavior is part of CLI setup. The reviewed runtime matches resolve to local logging and WebSocket support, so the scanner signals do not establish an attack surface.
Static reason
One or more suspicious static signals were detected.
Trigger
Running the CLI commands that set up agent skills or scaffold a project; no package install hook activates them.
Impact
No confirmed unauthorized credential transfer, account action, or agent control-surface mutation was established.
Mechanism
Setup records selected agents and updates a managed block in the project AGENTS.md. Session logging writes local files and rotates them; the inspected WebSocket code sets connection headers.
AI rationale
The package has no install-time activation, and the flagged agent configuration behavior is part of CLI setup. The reviewed runtime matches resolve to local logging and WebSocket support, so the scanner signals do not establish an attack surface.
Decision evidence
public snapshotAI called this Clean at 93.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json exposes a CLI and build entrypoint; its only publish lifecycle script runs clean and build commands, with no install hook.
- The flagged agent integrations support explicit CLI setup: they detect agent directories, record selected skill links in a project cache, and manage a marked block in the project AGENTS.md.
- The account-action matches resolve to local log rotation and session logging; the telemetry bundle includes the same local session behavior.
- The WebSocket match sets protocol and origin headers, and the help and command lookup matches are ordinary CLI support code.
Evidence against
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetwork
HighEntropyStringsMinifiedUrlStrings
Source & flagged code
9 flaggedbuild/cli/8796.index.jsView file
97const exec = await resolution.load();
L98: await exec(resolution.argv);
L99: return;
High
Child Process
Package source references child process execution.
build/cli/8796.index.jsView on unpkg · L97build/cli/8734.index.jsView file
5035L5036: module.exports = eval("require")("bufferutil");
L5037:
Low
Eval
Package source references a known benign dynamic code generation pattern.
build/cli/8734.index.jsView on unpkg · L5035bin/cli.jsView file
2L3: require('../build/cli');
Medium
Findings
6 High5 Medium6 Low
HighChild Processbuild/cli/8796.index.js
HighSame File Env Network Executionbuild/cli/index.js
HighCommand Output Exfiltrationbuild/telemetry/index.js
HighExternal Ai Agent Control Surface Mutationbuild/cli/7248.index.js
HighRuntime Package Installbuild/cli/2461.index.js
HighSemantic Analysis Limitedbuild/cli/1447.index.js#virtual:normalized:round1
MediumDynamic Requirebin/cli.js
MediumNetwork
MediumEnvironment Vars
MediumOversized Source Filebuild/cli/8103.index.js
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
Affected versions and remediation
This report applies to @expo/agent-cli@1.0.19.
See all versions of @expo/agent-cli for other recorded verdicts.
- Review the evidence and your use of @expo/agent-cli@1.0.19 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.