registry / @factory/cli / 0.240.1
@factory/cli@0.240.1
Factory Droid CLI - AI-powered software engineering agent
AI Security Review
scanned 22d ago · by lpm-firewall-aiThe lifecycle behavior is limited to obtaining and setting up the CLI’s version-matched platform binary, and the launcher passes user-supplied arguments to that binary. The inspected JavaScript source provides no concrete attack behavior.
Static reason
One or more suspicious static signals were detected.
Trigger
The package postinstall hook runs during installation; fallback downloading occurs if the optional platform binary is missing.
Impact
This prepares the advertised CLI binary. The inspected source did not establish unrelated file changes, credential disclosure, or an unrelated account action.
Mechanism
The installer obtains the matching binary from npm registry metadata, writes it under this package’s bin directory, and links the package’s launcher to it where supported.
AI rationale
The lifecycle behavior is limited to obtaining and setting up the CLI’s version-matched platform binary, and the launcher passes user-supplied arguments to that binary. The inspected JavaScript source provides no concrete attack behavior.
Evidence
bin/droid
Network endpoints1
registry.npmjs.org
Decision evidence
public snapshotAI called this Clean at 95.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest runs install.js after installation and declares vendor platform binaries as optional dependencies.
- If a platform binary is missing, the installer retrieves its tarball URL from npm registry metadata for the package version.
- The fallback extracts the selected binary into this package’s bin directory.
- The installer validates the binary and links it to this package’s launcher shim where supported.
- The launcher selects a platform binary and forwards the user’s command-line arguments to it.
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.240.1.
See all versions of @factory/cli for other recorded verdicts.
- Review the evidence and your use of @factory/cli@0.240.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.