droid@0.228.1
Factory Droid CLI - AI-powered software engineering agent
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe lifecycle behavior is package-aligned platform-binary setup and the fallback is restricted to npm registry metadata for the selected dependency. No concrete malicious behavior was found in the required source paths.
Static reason
One or more suspicious static signals were detected.
Trigger
Installing the package runs its postinstall hook.
Impact
It may create or link the package's CLI binary, with no confirmed effect outside the package installation.
Mechanism
The hook selects an installed platform dependency or downloads the matching platform package from the npm registry as a fallback.
AI rationale
The lifecycle behavior is package-aligned platform-binary setup and the fallback is restricted to npm registry metadata for the selected dependency. No concrete malicious behavior was found in the required source paths.
Network endpoints1
registry.npmjs.org/
Decision evidence
public snapshotAI called this Clean at 90.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The package invokes a postinstall installer and pins its platform-specific optional dependencies to this release.
- The installer uses the installed platform binary and only falls back to downloading the matching platform package when it is absent.
- The fallback obtains package metadata from the npm registry and writes the extracted binary under the package directory.
- No source evidence shows credential harvesting, foreign configuration changes, or data exfiltration.
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.228.1.
See all versions of droid for other recorded verdicts.
- Review the evidence and your use of droid@0.228.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.