registry / @expo/agent-cli / 1.0.10
@expo/agent-cli@1.0.10
Agent-native CLI on top of the Expo CLI family
AI Security Review
scanned 24d ago · by lpm-firewall-aiSource inspection found guarded, user-invoked agent plugin and skills setup, plus project guidance updates. No concrete malicious behavior was established, but the package-owned agent extension lifecycle capability warrants a warning.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
A user runs the agent setup command and confirms its plan, or uses its explicit yes option.
Impact
The selected agent's available extensions or project instructions may change within the chosen setup scope.
Mechanism
The confirmed plan invokes agent installers and may write an Expo-managed block to the project AGENTS.md file.
AI rationale
Source inspection found guarded, user-invoked agent plugin and skills setup, plus project guidance updates. No concrete malicious behavior was established, but the package-owned agent extension lifecycle capability warrants a warning.
Evidence
build/cli/217.index.jsbuild/cli/248.index.jsbuild/cli/271.index.jsbuild/cli/461.index.jspackage.jsonAGENTS.md
Decision evidence
public snapshotAI called this Suspicious at 86.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The package has a prepublishOnly build hook, with no preinstall, install, or postinstall hook declared in package.json.
- Agent setup requires confirmation before installers or file writers run, and stops when the plan is not confirmed.
- Confirmed setup can install agent plugins or skills and update project agent guidance, making this a guarded agent-extension setup capability.
- The inspected integration code targets project or user agent locations and manages an AGENTS.md block; the excerpts show no credential forwarding or covert write.
Evidence against
- The package does not declare an npm install-time lifecycle hook that activates the agent setup behavior.
Behavioral surface
ChildProcessCryptoEnvironmentVarsEvalFilesystemNetwork
HighEntropyStringsMinifiedUrlStrings
Source & flagged code
7 flaggedbuild/cli/510.index.jsView file
•matchType = previous_version_dangerous_delta
matchedPackage = @expo/agent-cli@1.0.8
matchedIdentity = npm:QGV4cG8vYWdlbnQtY2xp:1.0.8
similarity = 0.571
summary = stored previous version shares package body but lacks this dangerous source file
Critical
Previous Version Dangerous Delta
This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
build/cli/510.index.jsView on unpkg77L78: // EXTERNAL MODULE: external "child_process"
L79: var external_child_process_ = __webpack_require__(5317);
High
Child Process
Package source references child process execution.
build/cli/510.index.jsView on unpkg · L772051}
L2052: const result = await spawn('npx', ['--yes', 'expo-go', 'url', platform, sdkVersion, '--json'], {
L2053: timeoutMs: EXPO_GO_CLI_TIMEOUT_MS,
High
Runtime Package Install
Package source invokes a package manager install command at runtime.
build/cli/510.index.jsView on unpkg · L2051Findings
1 Critical5 High3 Medium6 Low
CriticalPrevious Version Dangerous Deltabuild/cli/510.index.js
HighChild Processbuild/cli/510.index.js
HighSame File Env Network Executionbuild/cli/index.js
HighExternal Ai Agent Control Surface Mutationbuild/cli/248.index.js
HighRuntime Package Installbuild/cli/510.index.js
HighSemantic Analysis Limitedbuild/cli/193.index.js#virtual:normalized:round1
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
LowEvalbuild/cli/734.index.js
LowFilesystem
Affected versions and remediation
This report applies to @expo/agent-cli@1.0.10.
See all versions of @expo/agent-cli for other recorded verdicts.
- Review the evidence and your use of @expo/agent-cli@1.0.10 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.