droid@0.238.0
Factory Droid CLI - AI-powered software engineering agent
AI Security Review
scanned 25d ago · by lpm-firewall-aiThe installer exposes NPM_TOKEN to a redirect destination selected through registry metadata when that destination's hostname contains npmjs.org. This is a conditional credential-forwarding risk, while the remaining install behavior is consistent with setting up the package's own CLI binary.
Decision evidence
public snapshot- package.json runs install.js automatically during postinstall and declares matching platform packages.
- install.js attaches NPM_TOKEN to requests when the hostname merely contains npmjs.org.
- Registry metadata supplies the tarball URL, and redirects are followed recursively without constraining the destination.
- The fallback download and shim replacement are limited to the package's platform binary and bin/droid.
- The postinstall is consistent with installing and optimizing this CLI's matching platform binary.
- The observed risk depends on NPM_TOKEN being set and a registry response redirecting to a hostname that passes the substring check.
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.238.0.
See all versions of droid for other recorded verdicts.
- Review the evidence and your use of droid@0.238.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.