droid@0.243.1
Factory Droid CLI - AI-powered software engineering agent
AI Security Review
scanned 19d ago · by lpm-firewall-aiThe lifecycle and native download are consistent with installing this CLI's version-matched platform binary from npm. The fallback lacks a source-level integrity check, but the inspected behavior does not establish a concrete attack surface.
Static reason
One or more suspicious static signals were detected.
Trigger
Package installation runs the postinstall hook.
Impact
This supports normal CLI installation; the inspected source shows no unrelated data collection, persistence, or destructive action.
Mechanism
The hook can fetch the selected platform package from the npm registry, extract its binary, and link it to the droid command shim.
AI rationale
The lifecycle and native download are consistent with installing this CLI's version-matched platform binary from npm. The fallback lacks a source-level integrity check, but the inspected behavior does not establish a concrete attack surface.
Evidence
bin/droid
Network endpoints1
registry.npmjs.org
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The postinstall hook is paired with optional platform packages pinned to version 0.243.1.
- When a platform package is missing, the fallback requests package metadata from registry.npmjs.org and selects the requested version.
- The fallback extracts the platform binary from that package tarball; the installer links it to the command shim.
Evidence against
- The postinstall fallback downloads and extracts a native executable without an integrity check in the inspected source.
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.243.1.
See all versions of droid for other recorded verdicts.
- Review the evidence and your use of droid@0.243.1 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.