droid@0.212.1
Factory Droid CLI - AI-powered software engineering agent
AI Security Review
scanned 2mo ago · by lpm-firewall-aiSource inspection shows a conventional native-CLI installer: pinned same-version platform packages, a registry fallback, and replacement of its own command shim. The token header is restricted to npmjs.org, and no credential harvesting, exfiltration, persistence, or broad configuration mutation is present.
Decision evidence
public snapshot- The manifest runs install.js automatically after installation.
- The installer can fetch a platform binary from the npm registry and write it into its own bin directory.
- The installer conditionally sends an npm token only to an npmjs.org host.
- The only declared dependencies are same-version, platform-specific @factory CLI packages.
- Postinstall replaces only this package's droid shim with the selected local binary.
- No source reads project files, shell profiles, credentials beyond the npm token, or writes agent configuration.
Source & flagged code
7 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.212.1.
See all versions of droid for other recorded verdicts.
- Review the evidence and your use of droid@0.212.1 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.