droid@1.2.0
Factory Droid CLI - AI-powered software engineering agent
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe lifecycle script performs setup for the package's advertised native CLI, using platform-specific optional dependencies and an npm-registry fallback. The NPM token path is scoped to hosts containing npmjs.org, and the reviewed source shows no unrelated collection or account actions.
Static reason
One or more suspicious static signals were detected.
Trigger
npm postinstall, or a user invoking the droid command.
Impact
Normal installation and execution of the Factory Droid CLI; no unrelated data collection or account action was found.
Mechanism
The hook uses an installed optional dependency or downloads the matching binary package from the npm registry as a fallback, then links the binary to the command shim.
AI rationale
The lifecycle script performs setup for the package's advertised native CLI, using platform-specific optional dependencies and an npm-registry fallback. The NPM token path is scoped to hosts containing npmjs.org, and the reviewed source shows no unrelated collection or account actions.
Evidence
bin/droidbin/droid.backup
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 selects platform-specific optional CLI binary packages.
- The installer uses NPM_TOKEN only for requests whose hostname contains npmjs.org.
- If an optional binary is missing, the installer fetches its tarball URL from registry.npmjs.org.
- The install hook links the CLI binary to bin/droid; the command shim forwards user arguments to that binary.
Evidence against
- The package runs a postinstall hook that accesses the network and writes under its own bin directory.
- Some platform binary dependency contents were unavailable for inspection.
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@1.2.0.
See all versions of droid for other recorded verdicts.
- Review the evidence and your use of droid@1.2.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.