droid@0.250.0
⚠ Under reviewFactory Droid CLI - AI-powered software engineering agent
AI Security Review
scanned 8d ago · by lpm-firewall-aiThe inspected lifecycle source is consistent with installing and selecting a platform-specific CLI binary, and it shows no confirmed attack behavior. Several relevant optional binary dependency snapshots are unresolved, so a clean verdict is not supported by this inspection.
Decision evidence
public snapshot- The postinstall hook selects a platform-specific optional binary package, but the supplied snapshots for relevant native packages are unresolved.
- If an optional binary is missing, the installer fetches its npm tarball and later executes the binary to check its version.
- The manifest pins platform-specific optional packages to this release, and the installer’s fallback fetch uses the npm registry.
- The inspected installer code shows no separate persistence, credential collection, or unrelated destination.
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.250.0.
See all versions of droid for other recorded verdicts.
- Review the evidence and your use of droid@0.250.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.