droid@0.226.0
Factory Droid CLI - AI-powered software engineering agent
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe postinstall script is a package-aligned native-binary shim, matching the esbuild-style optional-dependency layout declared in package.json. Registry access, the npm token, and file writes stay on the Factory CLI install path and do not mutate a foreign agent control surface.
Static reason
One or more suspicious static signals were detected.
Trigger
npm postinstall runs node install.js after a normal install.
Impact
The consumer gets the droid CLI binary. No foreign agent config, credential export, or project-wide mutation was found.
Mechanism
The script resolves a same-version @factory/cli platform package, optionally fetches its tarball from the npm registry, writes the binary under this package's bin directory, and hard-links it to bin/droid.
AI rationale
The postinstall script is a package-aligned native-binary shim, matching the esbuild-style optional-dependency layout declared in package.json. Registry access, the npm token, and file writes stay on the Factory CLI install path and do not mutate a foreign agent control surface.
Evidence
bin/droidbin/droid.backup
Network endpoints1
registry.npmjs.org
Decision evidence
public snapshotAI called this Clean at 86.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- postinstall runs node install.js and optionalDependencies are same-version @factory/cli platform packages.
- install.js replaces only this package's bin/droid with a hard link or symlink to the platform binary, then checks --version.
- If the optional package is missing, it downloads that package tarball from registry.npmjs.org and extracts package/bin into its own bin directory.
- NPM_TOKEN is attached only when the request hostname includes npmjs.org. PATH warnings print text and do not edit shell profiles.
Evidence against
- postinstall can download and execute a native binary and follows HTTP redirects without rechecking the host.
- The binary itself is not in this package, so its runtime behavior cannot be reviewed here.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
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.226.0.
See all versions of droid for other recorded verdicts.
- Review the evidence and your use of droid@0.226.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.