droid@0.219.0
Factory Droid CLI - AI-powered software engineering agent
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe install-time download and executable setup are notable but are narrowly tied to fixed same-vendor platform packages and the package's CLI. Static inspection found no concrete malicious behavior or lifecycle self-dependency chain.
Decision evidence
public snapshot- The postinstall hook automatically runs install.js.
- When optional dependencies are absent, the installer fetches a same-version platform package from the npm registry and writes its binary.
- The installer can send NPM_TOKEN only to an npmjs.org host.
- The install hook replaces its own bin/droid shim with a link to the platform binary.
- The fetched package is selected from the package's fixed same-vendor platform mapping.
- No self-dependency, secret harvesting, non-registry endpoint, evaluator-directed text, or foreign configuration write was found.
- The binary execution path is the user-invoked droid command.
Source & flagged code
6 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.219.0.
See all versions of droid for other recorded verdicts.
- Review the evidence and your use of droid@0.219.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.