droid@0.248.0
⚠ Under reviewFactory Droid CLI - AI-powered software engineering agent
AI Security Review
scanned 13d ago · by lpm-firewall-aiThe inspected wrapper shows package-aligned binary setup, but the selected native dependency source is outside the reviewed files. That unresolved executable behavior prevents a clean verdict; the inspected source does not establish a concrete attack.
Static reason
One or more suspicious static signals were detected.
Trigger
Package installation runs the postinstall hook; invoking droid launches the selected platform binary.
Impact
The native executable’s behavior remains unresolved, so this source review cannot determine whether it creates additional risk.
Mechanism
The installer can retrieve a platform package from the npm registry, extract its executable, and link it as the command. The launcher delegates execution to that binary.
AI rationale
The inspected wrapper shows package-aligned binary setup, but the selected native dependency source is outside the reviewed files. That unresolved executable behavior prevents a clean verdict; the inspected source does not establish a concrete attack.
Evidence
package.jsoninstall.jsplatform.jsbin/droid
Network endpoints1
registry.npmjs.org
Decision evidence
public snapshotAI called this Manual Review at 88.0% confidence as Unknown with medium false-positive risk.
AI review observations
- The manifest runs install.js during postinstall and declares platform-specific optional binary packages.
- The installer can fetch a platform package from npm, extract its executable, and write it into the package’s bin directory.
- The installer may run the binary during setup and link it as the droid command; the command shim also launches that binary.
- The reviewed JavaScript selects an external platform binary, whose behavior is not established by these source files.
Evidence against
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@0.248.0.
See all versions of droid for other recorded verdicts.
- Review the evidence and your use of droid@0.248.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.