registry / @factory/cli / 0.228.0
@factory/cli@0.228.0
Factory Droid CLI - AI-powered software engineering agent
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe postinstall behavior matches a documented optional-binary CLI shim: it fetches only the matching @factory platform package from the npm registry and links it inside this package. Credential use is limited to NPM_TOKEN on npmjs.org hosts, and the PATH message does not write agent or shell config.
Static reason
One or more suspicious static signals were detected.
Trigger
npm postinstall runs node install.js after a normal install of this package.
Impact
The package directory gains its own CLI binary. No foreign agent config, credential export, or consumer-project mutation was found.
Mechanism
The script resolves a same-vendor optional platform package, falls back to a registry.npmjs.org tarball of that package, and hardlinks or symlinks the binary over bin/droid.
AI rationale
The postinstall behavior matches a documented optional-binary CLI shim: it fetches only the matching @factory platform package from the npm registry and links it inside this package. Credential use is limited to NPM_TOKEN on npmjs.org hosts, and the PATH message does not write agent or shell config.
Decision evidence
public snapshotAI called this Clean at 86.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- postinstall runs node install.js to wire the droid CLI binary.
- If the platform optional dependency is missing, install.js downloads that same-version @factory platform package from registry.npmjs.org and writes it under the package bin directory.
- NPM_TOKEN is sent only as a Bearer header when the request hostname contains npmjs.org.
- On Unix the script replaces bin/droid with a hard link or symlink to that local platform binary and only prints a PATH hint without editing shell profiles.
Evidence against
- The registry client follows HTTP redirects, and the npmjs.org check is a substring match rather than an exact host allowlist.
- postinstall can execute the extracted platform binary with --version after writing it mode 0755.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
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.228.0.
See all versions of @factory/cli for other recorded verdicts.
- Review the evidence and your use of @factory/cli@0.228.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.