droid@0.242.0
Factory Droid CLI - AI-powered software engineering agent
AI Security Review
scanned 21d ago · by lpm-firewall-aiThe postinstall download and executable write are package-aligned setup for the declared platform-specific CLI dependencies. Although this fallback does not verify a tarball integrity value in the inspected code, no concrete attack behavior was established.
Decision evidence
public snapshot- The manifest runs install.js after installation and declares matching-version platform binaries as optional dependencies.
- If an optional binary is missing, install.js selects a platform package and retrieves its release metadata from the npm registry.
- The fallback extracts the expected platform binary from the package tarball and writes it to the local bin directory.
- The installer links the binary to the command shim when optimization is supported.
- The postinstall fallback downloads and installs an executable without checking the tarball against an integrity value in this code.
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.242.0.
See all versions of droid for other recorded verdicts.
- Review the evidence and your use of droid@0.242.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.