@expo/agent-cli@1.0.15
Agent-native CLI on top of the Expo CLI family
AI Security Review
scanned 17d ago · by lpm-firewall-aiThe manifest contains no install hook, and the flagged agent configuration behavior is exposed through an explicit setup command that writes a managed project instructions block. The remaining inspected runtime excerpts concern local logging, WebSocket handling, device inspection, and skill follow-up behavior; they do not establish malicious activity.
Decision evidence
public snapshot- package.json defines the CLI entrypoints and only a prepublishOnly hook, which runs clean and builds the package.
- Agent setup is exposed as an explicit agents:setup command; its code writes a managed block to the project AGENTS.md file.
- The setup code targets agent skill directories, while the agent registry identifies conventional project and user configuration locations.
- The flagged runtime bytes implement local log rotation and a session event logger; the WebSocket excerpt handles protocol headers.
- Other flagged chunks implement Expo Go device inspection, skill-sync follow-up reporting, and local device probing.
Source & flagged code
7 flaggedPackage source references child process execution.
build/cli/824.index.jsView on unpkg · L842Package source references a known benign dynamic code generation pattern.
build/cli/734.index.jsView on unpkg · L5035Findings
Affected versions and remediation
This report applies to @expo/agent-cli@1.0.15.
See all versions of @expo/agent-cli for other recorded verdicts.
- Review the evidence and your use of @expo/agent-cli@1.0.15 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.