droid@0.204.0
Factory Droid CLI - AI-powered software engineering agent
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe code presents a concrete conditional credential-forwarding weakness in an automatic lifecycle path, but static inspection does not establish an active malicious recipient or payload. This warrants a warning rather than a block.
Decision evidence
public snapshot- The manifest automatically runs install.js after installation.
- The installer forwards the existing npm token when a request hostname merely contains npmjs.org, rather than enforcing a bounded registry hostname.
- The request helper follows response-provided redirects, so a redirected download request reaches the same token-forwarding logic.
- The fallback download is only activated when the platform optional dependency is absent.
- The installer otherwise links the package-local command shim to its platform binary; no source evidence shows broad configuration changes or self-dependency.
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.204.0.
See all versions of droid for other recorded verdicts.
- Review the evidence and your use of droid@0.204.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.