@expo/agent-cli@1.0.0
Agent-native CLI on top of the Expo CLI family
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe package is not malicious by static inspection, but its explicit command changes AI-agent instruction and capability surfaces in a project. This warrants a warning under the agent-control policy rather than a publish block.
Decision evidence
public snapshot- The manifest has no install lifecycle hook; its only lifecycle script is prepublishOnly.
- The explicit agents:setup command can create or update a managed block in the project AGENTS.md.
- Explicit skill syncing can replace Expo-managed skill links in selected agent directories.
- The flagged ADB module resolves local SDK paths and environment variables.
- No install-time execution or runtime self-dependency is declared.
- AGENTS.md writes are limited to an explicit CLI command, preserve content outside managed markers, and reject symlinks.
- No credential harvesting or secret exfiltration was found in the inspected paths.
Source & flagged code
3 flaggedPackage source references a known benign dynamic code generation pattern.
build/cli/262.index.jsView on unpkg · L4969Runtime or CLI source writes behavior-bearing configuration into a user or project AI-agent control surface.
build/cli/159.index.jsFindings
Affected versions and remediation
This report applies to @expo/agent-cli@1.0.0.
See all versions of @expo/agent-cli for other recorded verdicts.
- Review the evidence and your use of @expo/agent-cli@1.0.0 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.