droid@0.239.1
Factory Droid CLI - AI-powered software engineering agent
AI Security Review
scanned 23d ago · by lpm-firewall-aiThe source shows a real but conditional token exposure risk because the fallback does not bind the destination host to the npm registry. The inspected code does not establish an actual disclosure or broader malicious behavior, so this warrants a warning rather than a block.
Decision evidence
public snapshot- The postinstall hook runs the installer, and platform-specific optional dependencies are declared at the same version.
- When a token is present, the installer adds it to requests for any hostname containing the npm registry’s domain text.
- The fallback takes the tarball URL from registry metadata and requests it, without checking that its host is the npm registry.
- The fallback runs when the platform binary is missing from optional dependencies.
- The fallback selects a platform package from a fixed mapping and requests the package’s matching version.
- The metadata lookup starts at the npm registry; the source does not establish that a non-registry host received a token.
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.239.1.
See all versions of droid for other recorded verdicts.
- Review the evidence and your use of droid@0.239.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.