registry / @factory/cli / 0.193.0
@factory/cli@0.193.0
Factory Droid CLI - AI-powered software engineering agent
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThe lifecycle behavior is a conventional optional-native-dependency fallback and self-contained launcher optimization. Source inspection found no concrete malicious chain.
Static reason
One or more suspicious static signals were detected.
Trigger
npm postinstall; later explicit droid invocation
Impact
Installs or links the CLI's platform binary; no foreign configuration or data is touched.
Mechanism
registry fallback download and local launcher linking
AI rationale
The lifecycle behavior is a conventional optional-native-dependency fallback and self-contained launcher optimization. Source inspection found no concrete malicious chain.
Evidence
package.jsoninstall.jsplatform.jsbin/droidbin/droid.backupbin/droid.exe
Network endpoints1
registry.npmjs.org/
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 runs install.js as postinstall.
- install.js can fetch a missing platform binary from registry.npmjs.org.
- install.js replaces its own bin/droid shim with a link to that binary.
Evidence against
- Download is limited to named @factory platform packages at the manifest version.
- NPM_TOKEN is sent only to npmjs.org, not arbitrary redirect hosts.
- No harvesting, exfiltration, eval, agent-config writes, or shell-profile mutation exists.
- bin/droid only launches the selected local platform binary with user arguments.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
NoLicense
Source & flagged code
6 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
5 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
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to @factory/cli@0.193.0.
See all versions of @factory/cli for other recorded verdicts.
- Review the evidence and your use of @factory/cli@0.193.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.