registry / @factory/cli / 0.212.1
@factory/cli@0.212.1
Factory Droid CLI - AI-powered software engineering agent
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe lifecycle download is a package-aligned fallback for exact-version platform binaries and writes only under the package directory. Source inspection found no broad persistence, credential exfiltration, remote code evaluation, or foreign control-surface mutation.
Static reason
One or more suspicious static signals were detected.
Trigger
npm postinstall for this package when its platform binary is missing.
Impact
Installs or links the package's native droid executable; no consumer-project, agent-control, or profile modification is performed.
Mechanism
package-local platform binary fallback and CLI shim optimization.
AI rationale
The lifecycle download is a package-aligned fallback for exact-version platform binaries and writes only under the package directory. Source inspection found no broad persistence, credential exfiltration, remote code evaluation, or foreign control-surface mutation.
Decision evidence
public snapshotAI called this Clean at 89.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The automatic postinstall can download and install a platform binary when the matching optional dependency is absent.
- The fallback writes the downloaded executable only into this package's bin directory.
Evidence against
- The download is limited to the package's exact-version, platform-specific @factory/cli dependencies from npm.
- The lifecycle code only links or restores this package's droid shim; it does not alter agent settings, shell profiles, or consumer-project files.
- NPM_TOKEN is conditionally sent only to an npmjs.org host; no other credential collection or exfiltration is present.
- The command shim executes the selected platform binary only when the user invokes droid.
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.212.1.
See all versions of @factory/cli for other recorded verdicts.
- Review the evidence and your use of @factory/cli@0.212.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.