registry / @factory/cli / 0.206.0
@factory/cli@0.206.0
Factory Droid CLI - AI-powered software engineering agent
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe postinstall behavior is a package-aligned native CLI shim, in the same pattern as optional platform binaries, and stays inside this package plus the npm registry. Credential use is limited to npmjs.org and no agent-config or exfiltration chain is present.
Static reason
One or more suspicious static signals were detected.
Trigger
npm postinstall runs node install.js after the package is installed.
Impact
The installed CLI uses its native binary. No foreign agent control surface, secret export, or consumer-project mutation was found.
Mechanism
The script resolves or downloads the same-version platform binary from registry.npmjs.org, writes it inside the package bin directory, and hardlinks the local shim. PATH issues are printed only.
AI rationale
The postinstall behavior is a package-aligned native CLI shim, in the same pattern as optional platform binaries, and stays inside this package plus the npm registry. Credential use is limited to npmjs.org and no agent-config or exfiltration chain is present.
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 and declares same-version @factory platform optionalDependencies.
- Fallback download requests the selected platform package packument only at registry.npmjs.org.
- NPM_TOKEN is attached only when the request hostname includes npmjs.org.
- The extracted binary is written under this package bin directory and the package shim is replaced with a hard link to it.
- A missing global PATH entry only prints shell advice; the function does not write profile files.
Evidence against
- Optional dependencies are sibling platform packages, not another release of @factory/cli.
- No writes to foreign agent configs, credential harvest, or unrelated network recipients appear in the install path.
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.206.0.
See all versions of @factory/cli for other recorded verdicts.
- Review the evidence and your use of @factory/cli@0.206.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.