droid@1.1.0
Factory Droid CLI - AI-powered software engineering agent
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe automatic install and native binary execution serve the package’s stated CLI purpose. The NPM token is conditionally attached to npmjs.org requests, and the inspected sources show no unrelated collection or account actions.
Static reason
One or more suspicious static signals were detected.
Trigger
npm postinstall; later, when the user invokes droid.
Impact
The package installs and runs its intended CLI binary; no unrelated data collection or account action was found.
Mechanism
The hook uses an installed optional dependency or downloads the matching binary from the npm registry, then validates and links it for CLI use.
AI rationale
The automatic install and native binary execution serve the package’s stated CLI purpose. The NPM token is conditionally attached to npmjs.org requests, and the inspected sources show no unrelated collection or account actions.
Evidence
bin/droidbin/droid.backup
Network endpoints1
registry.npmjs.org
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest identifies this as Factory Droid CLI and exposes a platform resolver and droid command.
- The postinstall fallback fetches the selected platform package’s tarball from the npm registry and extracts only its droid binary into the package’s bin directory.
- NPM_TOKEN is added to requests only when the requested hostname includes npmjs.org; the registry URL is constructed as registry.npmjs.org.
- The installer’s automatic binary check invokes only --version, and the command shim runs the CLI binary when the user invokes droid.
Evidence against
- A postinstall hook runs automatically, and the installer may download and execute a platform binary to prepare the CLI.
- The installer changes bin/droid by linking the native executable in place of the JavaScript shim.
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@1.1.0.
See all versions of droid for other recorded verdicts.
- Review the evidence and your use of droid@1.1.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.