registry / @factory/cli / 0.243.0
@factory/cli@0.243.0
Factory Droid CLI - AI-powered software engineering agent
AI Security Review
scanned 20d ago · by lpm-firewall-aiThe install-time download and shim replacement are scoped to the CLI's version-matched platform binaries and its own command entrypoint. The inspected source supports ordinary product setup, with no confirmed attack surface.
Static reason
One or more suspicious static signals were detected.
Trigger
The npm postinstall hook runs during package installation; its download fallback activates if no platform binary is found.
Impact
This supports the CLI's normal native-binary setup; the inspected source establishes no separate attack behavior.
Mechanism
The installer selects a platform-specific @factory/cli package, retrieves its binary, and links it as this package's command shim.
AI rationale
The install-time download and shim replacement are scoped to the CLI's version-matched platform binaries and its own command entrypoint. The inspected source supports ordinary product setup, with no confirmed attack surface.
Evidence
package.jsoninstall.jsplatform.jsbin/droid
Network endpoints1
registry.npmjs.org
Decision evidence
public snapshotAI called this Clean at 92.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json runs install.js after installation and pins platform-specific optional packages to version 0.243.0.
- platform.js maps supported platforms to matching @factory/cli binary packages.
- When an optional binary is missing, install.js selects the mapped platform package and retrieves its metadata from registry.npmjs.org.
- The fallback extracts the platform binary into this package's bin directory, and the installer replaces its own CLI shim with that binary.
- bin/droid forwards command-line arguments to the selected platform binary.
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.243.0.
See all versions of @factory/cli for other recorded verdicts.
- Review the evidence and your use of @factory/cli@0.243.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.