registry / @factory/cli / 0.231.0
@factory/cli@0.231.0
Factory Droid CLI - AI-powered software engineering agent
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe inspected source implements a transparent platform executable installer and launcher with package-local writes and npm-aligned authentication. Download hardening limitations do not establish an active attack or unrestricted operator-controlled credential forwarding.
Static reason
One or more suspicious static signals were detected.
Trigger
npm postinstall prepares the executable; invoking droid launches it.
Impact
Package-local executable setup and execution; no foreign agent configuration mutation or demonstrated credential exfiltration was identified.
Mechanism
The installer resolves an optional platform dependency or downloads its matching npm release, replaces the package-local shim, and checks the executable version.
AI rationale
The inspected source implements a transparent platform executable installer and launcher with package-local writes and npm-aligned authentication. Download hardening limitations do not establish an active attack or unrestricted operator-controlled credential forwarding.
Evidence
bin/droid
Network endpoints1
registry.npmjs.org/${encodedName}
Decision evidence
public snapshotAI called this Clean at 93.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json invokes install.js after installation and lists version-matched platform packages, without a runtime self-dependency.
- install.js selects a Factory platform package and obtains its matching release through registry.npmjs.org.
- install.js uses NPM_TOKEN for npm authentication; no operator-configured credential destination was identified.
- Installer writes and shim replacement remain inside the package's bin directory.
- platform.js resolves platform executables, and bin/droid launches the selected executable with command arguments.
Evidence against
- Fallback downloads lack an explicit integrity check, and the npm authentication hostname check uses substring matching.
- Platform executable dependencies are outside this snapshot, so their internals were not inspected.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetworkShell
HighEntropyStrings
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.231.0.
See all versions of @factory/cli for other recorded verdicts.
- Review the evidence and your use of @factory/cli@0.231.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.