droid@0.195.0
Factory Droid CLI - AI-powered software engineering agent
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThe package contains a concrete install-time remote native-payload path without explicit payload integrity verification. Its actions are otherwise package-local and no malicious exfiltration, persistence outside the package, or AI-agent control-surface tampering is present.
Decision evidence
public snapshot- postinstall invokes install.js.
- When its optional platform dependency is absent, the installer fetches a registry-selected tarball, extracts a native binary, and writes it executable.
- The fallback does not verify a tarball digest or signature before installing the binary.
- The lifecycle script only changes this package's bin/droid shim or its local bin directory.
- Network bootstrap is limited to the npm registry/tarball URL supplied by its packument.
- NPM_TOKEN is attached only when the current request host includes npmjs.org; no general credential harvesting or exfiltration was found.
- No source writes shell profiles, AI-agent configuration, or other foreign control surfaces.
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.195.0.
See all versions of droid for other recorded verdicts.
- Review the evidence and your use of droid@0.195.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.