@expo/agent-cli@1.0.5
Agent-native CLI on top of the Expo CLI family
AI Security Review
scanned 17d ago · by lpm-firewall-aiSource inspection found no install-time attack or unauthorized runtime action. The configuration changes are part of an explicit CLI setup command, and the runtime excerpts resolve to session logging and log rotation.
Decision evidence
public snapshot- The manifest exposes a CLI entrypoint and only a prepublishOnly build hook; it has no install lifecycle hook.
- The agent setup command is explicitly invoked and offers options to limit agent setup or skip AGENTS.md changes.
- The agent configuration excerpts define project-scoped skill directories and markers.
- The flagged runtime excerpts implement log segment rotation and session logging; they do not perform account actions.
- The Expo subprocess runs from a project command, and the inspected checks and spawn helpers are ordinary CLI behavior.
- Explicit agent setup can write a managed AGENTS.md block and create skill links in agent directories.
- The CLI can invoke npx expo during a project operation.
Source & flagged code
6 flaggedPackage source references child process execution.
build/cli/472.index.jsView on unpkg · L257Package source invokes a package manager install command at runtime.
build/cli/472.index.jsView on unpkg · L257Package source references a known benign dynamic code generation pattern.
Findings
Affected versions and remediation
This report applies to @expo/agent-cli@1.0.5.
See all versions of @expo/agent-cli for other recorded verdicts.
- Review the evidence and your use of @expo/agent-cli@1.0.5 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.