droid@0.245.1
⚠ Under reviewFactory Droid CLI - AI-powered software engineering agent
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe manifest and installer show a platform-binary setup path aligned with the CLI, but the native executable source is not included in the inspected snapshot. Because that unresolved runtime dependency prevents a clean determination, manual review is appropriate.
Static reason
One or more suspicious static signals were detected.
Trigger
Package installation; the fallback download runs if the optional platform binary is missing.
Impact
The behavior of the installed native executable cannot be determined from the inspected files.
Mechanism
The postinstall fetches the matching binary package from the npm registry, extracts its executable, and installs it for the command shim to use.
AI rationale
The manifest and installer show a platform-binary setup path aligned with the CLI, but the native executable source is not included in the inspected snapshot. Because that unresolved runtime dependency prevents a clean determination, manual review is appropriate.
Evidence
package.jsoninstall.jsplatform.jsbin/droidbin/droid.backupbin/droid.exe
Network endpoints1
registry.npmjs.org
Decision evidence
public snapshotAI called this Manual Review at 85.0% confidence as Unknown with medium false-positive risk.
AI review observations
- The manifest runs install.js after installation and declares same-version optional platform binaries.
- If an optional binary is missing, the installer fetches its package from the npm registry, extracts the executable, and writes it locally.
- The platform mapping selects the matching binary package, and the Unix installer links that binary into the droid command.
Evidence against
- The inspected JavaScript uses the registry fallback only when the optional platform binary is absent.
- The inspected package snapshot contains no native binary source to assess.
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.245.1.
See all versions of droid for other recorded verdicts.
- Review the evidence and your use of droid@0.245.1 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.