droid@0.209.1
Factory Droid CLI - AI-powered software engineering agent
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe lifecycle script downloads and links a platform-specific CLI binary, but its sources and writes are package-aligned and bounded. Static inspection found no concrete credential theft, exfiltration, persistence outside the package, or AI-agent control-surface mutation.
Decision evidence
public snapshot- The manifest automatically runs install.js after installation and declares exact-version platform binary packages.
- When a platform dependency is absent, the installer obtains the selected package through the npm registry and writes its droid binary inside this package.
- The installer restricts NPM_TOKEN authorization to npmjs.org hosts.
- The install-time file changes are limited to this package's bin/droid shim, backup, and platform binary.
- Platform packages are fixed same-vendor optional dependencies at version 0.209.1; there is no runtime dependency on droid itself.
- No source code harvests local credentials or files, modifies AI-agent settings, or exfiltrates data.
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.209.1.
See all versions of droid for other recorded verdicts.
- Review the evidence and your use of droid@0.209.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.