droid@0.251.0
⚠ Under reviewFactory Droid CLI - AI-powered software engineering agent
AI Security Review
scanned 8d ago · by lpm-firewall-aiThe inspected installer and launcher are consistent with setting up and running the platform-specific CLI, and do not establish malicious behavior. The native platform payload is not included in the inspected package snapshot, so review remains unresolved.
Static reason
One or more suspicious static signals were detected.
Trigger
Package installation runs the postinstall hook; the command shim runs when a user invokes droid.
Impact
The native binary's runtime behavior cannot be assessed from the available source.
Mechanism
The installer may download and extract a platform binary from the npm registry, then link it into the package's command path. The launcher executes that binary.
AI rationale
The inspected installer and launcher are consistent with setting up and running the platform-specific CLI, and do not establish malicious behavior. The native platform payload is not included in the inspected package snapshot, so review remains unresolved.
Evidence
package.jsoninstall.jsplatform.jsbin/droid
Network endpoints1
registry.npmjs.org
Decision evidence
public snapshotAI called this Manual Review at 84.0% confidence as Unknown with medium false-positive risk.
AI review observations
- The manifest runs install.js after installation and declares platform-specific native packages at the same version.
- If the platform package is missing, the installer downloads its tarball, extracts the platform binary, and writes it into the package's bin directory.
- The available source covers the JavaScript installer and launcher, but not the native binary payload supplied by the platform package.
Evidence against
- The installer selects a platform package and optimizes the package's own command shim; the inspected source does not establish a malicious action.
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.251.0.
See all versions of droid for other recorded verdicts.
- Review the evidence and your use of droid@0.251.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.