droid@0.205.0
Factory Droid CLI - AI-powered software engineering agent
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThis is a standard optional-native-binary CLI installer for Factory Droid. Registry download, token use, and bin linking are package-aligned 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; later the user invokes the droid bin.
Impact
The installed command runs the Factory CLI binary. No foreign agent config, secret export, or consumer-project mutation was found.
Mechanism
The script locates or downloads the same-version @factory platform package, writes it under the package bin directory, and links bin/droid to it. The shim then spawns that binary with the caller arguments.
AI rationale
This is a standard optional-native-binary CLI installer for Factory Droid. Registry download, token use, and bin linking are package-aligned and do not mutate a foreign agent control surface.
Decision evidence
public snapshotAI called this Clean at 86.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- postinstall only runs node install.js to wire the Factory CLI native binary.
- Optional dependencies are pinned same-version @factory/cli platform packages, not a nested release of droid.
- NPM_TOKEN is attached only when the request host contains npmjs.org.
- Fallback download fetches the matching platform package tarball from registry.npmjs.org and writes the binary inside this package bin directory.
- On Unix the postinstall replaces bin/droid with a hard link or symlink to that binary; PATH warnings only print text and do not edit shell profiles or agent configs.
- The bin/droid shim spawns the resolved platform binary with the user arguments and inherited stdio.
Evidence against
- No writes to foreign AI-agent control surfaces, no credential harvest beyond an npm registry auth header, and no self-dependency lifecycle chain.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetwork
HighEntropyStrings
Source & flagged code
6 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
5 High4 Medium5 Low
HighInstall Time Lifecycle Scriptspackage.json
HighChild Processinstall.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
LowNo License
Affected versions and remediation
This report applies to droid@0.205.0.
See all versions of droid for other recorded verdicts.
- Review the evidence and your use of droid@0.205.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.