droid@0.241.0
Factory Droid CLI - AI-powered software engineering agent
AI Security Review
scanned 22d ago · by lpm-firewall-aiThe installer has a conditional credential exposure risk: it uses a substring hostname check and follows redirects while forwarding NPM_TOKEN. The matching scoped binary packages and lack of source evidence for an unrelated destination keep this at suspicious rather than malicious.
Decision evidence
public snapshot- The postinstall fallback fetches a tarball URL supplied by npm registry metadata and passes it to the request helper.
- The request helper attaches NPM_TOKEN when the hostname contains “npmjs.org” and follows redirects recursively, so a lookalike hostname can receive the token if the fallback is triggered.
- The fallback runs when the platform binary is unavailable; source does not establish that this release sends the token to an unrelated host.
- The manifest pins platform binaries to matching 0.241.0 releases under the @factory scope.
- The installer writes the extracted binary into its own bin directory and links it to the package’s droid shim.
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.241.0.
See all versions of droid for other recorded verdicts.
- Review the evidence and your use of droid@0.241.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.