registry / @factory/cli / 0.236.0
@factory/cli@0.236.0
Factory Droid CLI - AI-powered software engineering agent
AI Security Review
scanned 17d ago · by lpm-firewall-aiThe postinstall activity is consistent with installing and optimizing this CLI’s platform binary, with same-version optional dependencies and an npm-registry fallback. The inspected source did not establish a concrete attack surface.
Static reason
One or more suspicious static signals were detected.
Trigger
Package installation runs the postinstall hook; the download fallback activates only when the platform binary is unavailable as an optional dependency.
Impact
This installs and selects the CLI executable; inspected source showed no unrelated file mutation or credential transfer.
Mechanism
The installer fetches package metadata and a platform-specific tarball, extracts the binary, and links it to the CLI shim on supported Unix systems.
AI rationale
The postinstall activity is consistent with installing and optimizing this CLI’s platform binary, with same-version optional dependencies and an npm-registry fallback. The inspected source did not establish a concrete attack surface.
Evidence
install.jsbin/droid
Network endpoints1
registry.npmjs.org
Decision evidence
public snapshotAI called this Clean at 92.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The postinstall hook runs the package’s installer, and platform binaries are declared as same-version optional dependencies.
- The installer’s fallback downloads a platform binary from the npm registry only when the optional dependency is missing, then writes it into the package’s bin directory.
- On supported Unix installs, the installer links the selected binary to the CLI shim; platform selection is based on the current platform and CPU support.
- No attack behavior was identified in the inspected lifecycle, entrypoint, or platform-selection code.
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 @factory/cli@0.236.0.
See all versions of @factory/cli for other recorded verdicts.
- Review the evidence and your use of @factory/cli@0.236.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.