droid@0.216.0
Factory Droid CLI - AI-powered software engineering agent
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe lifecycle behavior is a package-aligned native CLI installer with fixed same-version platform dependencies and a registry fallback. Although it downloads a native binary during installation, the inspected code does not establish malicious behavior.
Static reason
One or more suspicious static signals were detected.
Trigger
npm postinstall, when the platform optional dependency is missing.
Impact
It may place and execute the package's platform-specific CLI binary, but the inspected source shows no unrelated file mutation or data exfiltration.
Mechanism
Registry fallback download and local command-shim linking.
AI rationale
The lifecycle behavior is a package-aligned native CLI installer with fixed same-version platform dependencies and a registry fallback. Although it downloads a native binary during installation, the inspected code does not establish malicious behavior.
Evidence
bin/droidbin/droid.exe
Network endpoints1
registry.npmjs.org/
Decision evidence
public snapshotAI called this Clean at 90.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The postinstall hook can fetch an exact-version platform binary from the npm registry when its optional dependency is unavailable.
- The installer replaces only its own command shim with a link to the selected binary and checks that binary's version.
Evidence against
- Platform binary package names and versions are fixed in optional dependencies; there is no runtime dependency on droid itself.
- The only observed network source is the npm registry, used for the package's own platform binary fallback.
- No credential harvesting, non-registry exfiltration, broad project mutation, agent-control writes, or persistence behavior was found.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
NoLicense
Source & flagged code
7 flaggedpackage.jsonView file
•scripts.postinstall = node install.js
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg9scripts.postinstall = node install.js
Install-time code downloads an unverified remote native executable, stages it locally, activates an executable path, and exposes it to process execution.
L9: *
L10: * Based on esbuild's approach: https://github.com/evanw/esbuild/pull/1621
L11: * and Sentry's guide: https://sentry.engineering/blog/publishing-binaries-on-npm
L12: *
...
L19: const path = require('path');
L20: const https = require('https');
L21: const zlib = require('zlib');
...
L27: getBinaryName,
L28: getBinaryPath,
L29: detectAVX2Support,
...
L50:
L51: function validateBinaryVersion(binaryPath) {
High
Unverified Remote Native Payload Install
Install-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 · L9•scripts.postinstall = node install.js
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
Findings
6 High4 Medium5 Low
HighInstall Time Lifecycle Scriptspackage.json
HighChild Processinstall.js
HighShellinstall.js
HighSame File Env Network Executioninstall.js#virtual:normalized:round1
HighUnverified Remote Native Payload Installpackage.json
HighSemantic Analysis Limitedinstall.js#virtual:normalized:round1
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Low
Affected versions and remediation
This report applies to droid@0.216.0.
See all versions of droid for other recorded verdicts.
- Review the evidence and your use of droid@0.216.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.