droid@0.228.0
Factory Droid CLI - AI-powered software engineering agent
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe install script is a same-vendor native CLI shim, like esbuild, limited to this package bin and the npm registry. It does not mutate foreign agent configs or exfiltrate credentials.
Static reason
One or more suspicious static signals were detected.
Trigger
npm postinstall runs node install.js after a normal install.
Impact
Install optimizes the local droid command shim. No foreign agent control surface, credential export, or destructive change was found.
Mechanism
The script selects the same-version @factory platform package, optionally downloads its tarball from registry.npmjs.org, writes the binary into the package bin directory, and hard-links or symlinks bin/droid. PATH handling only logs advice.
AI rationale
The install script is a same-vendor native CLI shim, like esbuild, limited to this package bin and the npm registry. It does not mutate foreign agent configs or exfiltrate credentials.
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 install.js and declares same-version @factory/cli platform optionalDependencies.
- Fallback download requests registry.npmjs.org and writes the extracted binary only under this package bin directory.
- NPM_TOKEN is added only when the request hostname includes npmjs.org.
- On Unix the script replaces only its own bin/droid shim with a hard link or symlink to that binary.
- If the global bin directory is missing from PATH, the script only prints shell advice.
- Reviewed sources do not write agent configs, harvest unrelated credentials, or spawn remote payloads.
Evidence against
- The native droid binary lives in optional platform packages and is not present in this tarball, so its runtime behavior is outside this review.
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.228.0.
See all versions of droid for other recorded verdicts.
- Review the evidence and your use of droid@0.228.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.