registry / @factory/cli / 1.1.0
@factory/cli@1.1.0
Factory Droid CLI - AI-powered software engineering agent
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe postinstall network request retrieves the platform-specific @factory/cli binary from npm as a fallback, and the npm token is sent only to npmjs.org. File changes and process execution support installation and invocation of the CLI.
Static reason
One or more suspicious static signals were detected.
Trigger
The postinstall hook runs during installation; the executable runs when the user invokes droid.
Impact
Expected installation of the CLI executable and forwarding of user-supplied arguments to it.
Mechanism
The hook uses npm to obtain the matching platform binary when an optional dependency is unavailable, writes it under the package's bin directory, and optimizes the local shim. NPM_TOKEN is restricted to npmjs.org requests.
AI rationale
The postinstall network request retrieves the platform-specific @factory/cli binary from npm as a fallback, and the npm token is sent only to npmjs.org. File changes and process execution support installation and invocation of the CLI.
Evidence
bin/droid
Network endpoints1
registry.npmjs.org
Decision evidence
public snapshotAI called this Clean at 95.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The postinstall hook runs install.js; the manifest lists platform-specific @factory/cli binaries as optional dependencies.
- The fallback installer downloads the binary for the detected platform from npm and writes it into the package's bin directory.
- NPM_TOKEN is added only when the request hostname includes npmjs.org.
- The droid command selects and runs the platform binary with the user's supplied arguments.
Evidence against
- Install-time network access, environment-variable access and child-process execution are present, but the source ties them to binary installation and selection.
- The install hook replaces the package's own command shim with a link to that binary.
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@1.1.0.
See all versions of @factory/cli for other recorded verdicts.
- Review the evidence and your use of @factory/cli@1.1.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.