droid@0.209.0
Factory Droid CLI - AI-powered software engineering agent
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThis is a transparent, package-aligned native CLI installer with a version-pinned optional-dependency fallback. Its lifecycle behavior is notable but source inspection found no concrete malicious action.
Static reason
One or more suspicious static signals were detected.
Trigger
npm postinstall
Impact
Installs or links the package's own droid executable; no source-level evidence shows data theft or external persistence.
Mechanism
download and link a platform-specific CLI binary
AI rationale
This is a transparent, package-aligned native CLI installer with a version-pinned optional-dependency fallback. Its lifecycle behavior is notable but source inspection found no concrete malicious action.
Evidence
package.jsonplatform.jsbin/droid
Network endpoints1
registry.npmjs.org
Decision evidence
public snapshotAI called this Clean at 88.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The package runs install.js automatically after installation.
- The installer fetches a version-pinned platform package from the npm registry and writes its native binary locally.
- The installer replaces its own command shim with a link to that binary and runs it only for a version check.
Evidence against
- All install-time writes are confined to the package's bin directory.
- The only source-defined network host is the npm registry; the npm token is attached only for npmjs.org.
- No source reads user files, harvests credentials, changes agent settings, or persists outside the package.
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.209.0.
See all versions of droid for other recorded verdicts.
- Review the evidence and your use of droid@0.209.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.