registry / @factory/cli / 0.215.1
@factory/cli@0.215.1
Factory Droid CLI - AI-powered software engineering agent
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe lifecycle behavior is a transparent, package-scoped native-binary fallback and launcher optimization. Network, environment, and child-process use are limited to registry retrieval, npm authentication for the registry, platform detection, and binary version validation.
Static reason
One or more suspicious static signals were detected.
Trigger
npm postinstall when the matching optional platform dependency is absent.
Impact
It installs and validates a package-aligned executable; the source shows no credential theft, persistence outside the package, or broad configuration changes.
Mechanism
Registry fallback for a package-owned native CLI binary.
AI rationale
The lifecycle behavior is a transparent, package-scoped native-binary fallback and launcher optimization. Network, environment, and child-process use are limited to registry retrieval, npm authentication for the registry, platform detection, and binary version validation.
Evidence
bin/droidbin/<platform binary>
Network endpoints1
registry.npmjs.org/
Decision evidence
public snapshotAI called this Clean at 90.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The postinstall hook downloads and writes a platform binary when its optional dependency is unavailable.
- The installer forwards NPM_TOKEN only to npmjs.org and then executes the selected binary only for a version check.
Evidence against
- The lifecycle hook only replaces this package's bin/droid shim with a platform-specific optional-dependency binary.
- The fallback names exact same-version @factory platform packages and obtains metadata from the npm registry.
- No source reads arbitrary user files, exfiltrates data, alters shell profiles, or mutates AI-agent configuration.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetwork
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
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
LowNo License
Affected versions and remediation
This report applies to @factory/cli@0.215.1.
See all versions of @factory/cli for other recorded verdicts.
- Review the evidence and your use of @factory/cli@0.215.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.