registry / @expo/agent-cli / 1.0.20
@expo/agent-cli@1.0.20
Agent-native CLI on top of the Expo CLI family
AI Security Review
scanned 16d ago · by lpm-firewall-aiSource inspection supports a clean verdict: the manifest declares no npm install hook, and the inspected agent integration and runtime locations do not establish an attack. Scanner labels and bounded analysis limits were not treated as proof of malicious behavior.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The CLI is invoked by a user; the manifest's prepublishOnly hook runs build commands.
Impact
No malicious effect was established from the inspected source.
Mechanism
The inspected AGENTS.md code updates a delimited managed block. The runtime locations cited for account behavior are log rotation and session logging, not account changes.
AI rationale
Source inspection supports a clean verdict: the manifest declares no npm install hook, and the inspected agent integration and runtime locations do not establish an attack. Scanner labels and bounded analysis limits were not treated as proof of malicious behavior.
Evidence
AGENTS.md
Decision evidence
public snapshotAI called this Clean at 80.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest exposes a CLI and lists only a prepublishOnly build hook; it does not declare an install hook.
- The AGENTS.md code maintains a marked block and preserves content outside it; the agent integration excerpts identify project and home configuration paths.
- The cited runtime locations show log rotation and session logging, not account actions; the WebSocket excerpt constructs an Origin header from an option.
- The inspected smoke command and bundle excerpts do not establish a package-install attack.
Evidence against
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetwork
HighEntropyStringsMinifiedUrlStrings
Source & flagged code
10 flaggedbuild/cli/824.index.jsView file
182const command = `npx expo ${args.join(' ')}`;
L183: const built = await spawn('npx', ['expo', ...args], { cwd: projectRoot, timeoutMs });
L184: if (built.spawnError) {
High
Child Process
Package source references child process execution.
build/cli/824.index.jsView on unpkg · L182182const command = `npx expo ${args.join(' ')}`;
L183: const built = await spawn('npx', ['expo', ...args], { cwd: projectRoot, timeoutMs });
L184: if (built.spawnError) {
High
Runtime Package Install
Package source invokes a package manager install command at runtime.
build/cli/824.index.jsView on unpkg · L182build/cli/734.index.jsView file
5035L5036: module.exports = eval("require")("bufferutil");
L5037:
Low
Eval
Package source references a known benign dynamic code generation pattern.
Findings
1 Critical6 High5 Medium6 Low
CriticalPrevious Version Dangerous Deltabuild/cli/627.index.js
HighChild Processbuild/cli/824.index.js
HighSame File Env Network Executionbuild/cli/index.js
HighCommand Output Exfiltrationbuild/telemetry/index.js
HighExternal Ai Agent Control Surface Mutationbuild/cli/248.index.js
HighRuntime Package Installbuild/cli/824.index.js
HighSemantic Analysis Limitedbuild/cli/254.index.js#virtual:normalized:round1
MediumDynamic Requirebin/cli.js
MediumNetwork
MediumEnvironment Vars
MediumOversized Source Filebuild/cli/103.index.js
MediumStructural Risk Force Deep Review
Affected versions and remediation
This report applies to @expo/agent-cli@1.0.20.
See all versions of @expo/agent-cli for other recorded verdicts.
- Review the evidence and your use of @expo/agent-cli@1.0.20 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.