@expo/agent-cli@1.0.6
Agent-native CLI on top of the Expo CLI family
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe package contains an explicit, confirmation-gated agent extension installer rather than an automatic lifecycle attack. Its ability to modify agent configuration warrants a warning, but the inspected source does not establish malicious behavior.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
A user runs expo-agent-cli agents:setup and confirms the plan, or explicitly passes --yes with an agent.
Impact
It can add Expo capabilities to a selected coding agent and alter the managed block in the current Expo project instruction file.
Mechanism
External agent-plugin installation and managed AGENTS.md update.
AI rationale
The package contains an explicit, confirmation-gated agent extension installer rather than an automatic lifecycle attack. Its ability to modify agent configuration warrants a warning, but the inspected source does not establish malicious behavior.
Evidence
build/cli/271.index.jsAGENTS.md
Network endpoints1
github.com
Decision evidence
public snapshotAI called this Suspicious at 88.0% confidence as Dangerous Capability with low false-positive risk.
Evidence for warning
- The explicit agents:setup command can add the Expo marketplace from the main branch and install a Codex plugin.
- The setup command runs external installer commands and can update a project AGENTS.md file.
- The setup flow permits noninteractive execution when the caller supplies confirmation and an agent.
Evidence against
- The manifest has no install, preinstall, or postinstall hook; its only lifecycle hook is prepublishOnly.
- The agent setup flow returns without running installers unless its plan is confirmed.
- The observed fetch is limited to checking a configured local Expo development server status.
Behavioral surface
ChildProcessCryptoEnvironmentVarsEvalFilesystemNetwork
HighEntropyStringsMinifiedProtestwareUrlStrings
Source & flagged code
6 flaggedbuild/cli/472.index.jsView file
257const command = `npx expo ${args.join(' ')}`;
L258: const built = await spawn('npx', ['expo', ...args], { cwd: projectRoot, timeoutMs });
L259: if (built.spawnError) {
High
Child Process
Package source references child process execution.
build/cli/472.index.jsView on unpkg · L257257const command = `npx expo ${args.join(' ')}`;
L258: const built = await spawn('npx', ['expo', ...args], { cwd: projectRoot, timeoutMs });
L259: if (built.spawnError) {
High
Runtime Package Install
Package source invokes a package manager install command at runtime.
build/cli/472.index.jsView on unpkg · L257build/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 Critical4 High4 Medium6 Low
CriticalPrevious Version Dangerous Deltabuild/cli/71.index.js
HighChild Processbuild/cli/472.index.js
HighExternal Ai Agent Control Surface Mutationbuild/cli/271.index.js
HighRuntime Package Installbuild/cli/472.index.js
HighSemantic Analysis Limitedbuild/cli/246.index.js#virtual:normalized:round1
MediumNetwork
MediumEnvironment Vars
MediumProtestware
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
LowEvalbuild/cli/734.index.js
LowFilesystem
LowHigh Entropy Strings
Affected versions and remediation
This report applies to @expo/agent-cli@1.0.6.
See all versions of @expo/agent-cli for other recorded verdicts.
- Review the evidence and your use of @expo/agent-cli@1.0.6 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.