@expo/agent-cli@1.0.21
Agent-native CLI on top of the Expo CLI family
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe flagged telemetry is disclosed in the README, sends command-usage data to Expo’s telemetry service, and can be disabled with EXPO_NO_TELEMETRY or EXPO_OFFLINE. Agent instructions are written through the documented, explicit agents:setup command; no malicious behavior was identified.
Decision evidence
public snapshot- The package is an Expo CLI with a bin entry and bundled CLI main.
- The README discloses command-usage telemetry, its fields, exclusions, and the EXPO_NO_TELEMETRY or EXPO_OFFLINE opt-out.
- The telemetry worker sends command name and version with anonymous or hashed identity and runtime, agent, and sandbox context.
- Telemetry is launched as a detached worker after a command and honors the telemetry opt-out.
- The CLI describes agents:setup as a command that confirms agent setup; its managed-block writer updates AGENTS.md when invoked.
Source & flagged code
10 flaggedPackage source references child process execution.
build/cli/8796.index.jsView on unpkg · L97Package source references a known benign dynamic code generation pattern.
build/cli/8734.index.jsView on unpkg · L5035Findings
Affected versions and remediation
This report applies to @expo/agent-cli@1.0.21.
See all versions of @expo/agent-cli for other recorded verdicts.
- Review the evidence and your use of @expo/agent-cli@1.0.21 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.