droid@0.247.0
⚠ Under reviewFactory Droid CLI - AI-powered software engineering agent
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe inspected lifecycle code performs product-aligned binary setup, but the platform-specific executable dependencies were unresolved and absent from the snapshot. That leaves a selected executable boundary unreviewed, so the package cannot be cleared as clean from the available source.
Decision evidence
public snapshot- package.json runs install.js during postinstall and declares version-pinned platform-specific optional binary packages.
- The installer uses the optional binary when available and otherwise attempts an npm download.
- The fallback writes the extracted native executable into the package's bin directory.
- On Unix, postinstall links the selected binary over bin/droid.
- The selected native dependency source was unresolved in the supplied review records, so its behavior could not be assessed.
- The declared binary packages match the product name and package version.
- The inspected installer behavior is consistent with setting up the platform-specific CLI and optimizing its command shim.
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.247.0.
See all versions of droid for other recorded verdicts.
- Review the evidence and your use of droid@0.247.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.