droid@0.203.0
Factory Droid CLI - AI-powered software engineering agent
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe lifecycle behavior is a conventional native CLI bootstrap: it selects a declared platform package, falls back to that package's npm tarball, and relinks its own executable shim. Source inspection found no concrete credential exfiltration, destructive behavior, stealth persistence, or AI-agent control-surface mutation.
Decision evidence
public snapshot- Postinstall runs install.js.
- Fallback fetches a platform tarball from npm and writes its binary.
- Platform-specific native packages are declared as optional dependencies.
- Postinstall only relinks the package's own bin/droid shim.
- NPM_TOKEN is sent only for hosts containing npmjs.org.
- No source evidence of harvesting, exfiltration, persistence, or agent-config writes.
Source & flagged code
6 flaggedPackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time source downloads a native archive from a fixed external host without transport verification, extracts it, and installs an executable payload.
package.jsonView on unpkg · L9Install-time lifecycle script is not statically allowlisted and needs review.
Findings
Affected versions and remediation
This report applies to droid@0.203.0.
See all versions of droid for other recorded verdicts.
- Review the evidence and your use of droid@0.203.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.