droid@0.218.0
Factory Droid CLI - AI-powered software engineering agent
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThis is a transparent native-CLI installer with package-local writes and a registry fallback, not a concrete malicious chain. The lifecycle and remote binary retrieval are supply-chain risk primitives but are aligned with the CLI’s stated packaging structure.
Decision evidence
public snapshot- The postinstall hook downloads a platform binary when its optional dependency is unavailable.
- The hook writes and links only the package’s own bin/droid path.
- The manifest pins platform-specific optional dependencies to the same release.
- Network access is limited to retrieving the selected platform package from the npm registry.
- The npm token is attached only to npmjs.org requests; no other credential collection or upload is present.
- No self-dependency, broad project mutation, persistence, or agent-control configuration writes were found.
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.218.0.
See all versions of droid for other recorded verdicts.
- Review the evidence and your use of droid@0.218.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.