registry / @factory/cli / 0.241.0
@factory/cli@0.241.0
Factory Droid CLI - AI-powered software engineering agent
AI Security Review
scanned 22d ago · by lpm-firewall-aiThe inspected install behavior is consistent with setting up the package's version-matched platform binary and CLI shim. Although the fallback does not verify a content hash, the source shows no concrete attack behavior.
Static reason
One or more suspicious static signals were detected.
Trigger
Package installation runs the postinstall hook; the download fallback is used if the platform binary is unavailable.
Impact
The package installs and optimizes its intended CLI executable; no malicious impact is established by the inspected source.
Mechanism
The installer requests the matching platform package version, extracts its binary, and links the selected binary to the droid command shim.
AI rationale
The inspected install behavior is consistent with setting up the package's version-matched platform binary and CLI shim. Although the fallback does not verify a content hash, the source shows no concrete attack behavior.
Evidence
install.jsbin/droid
Network endpoints1
registry.npmjs.org
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The postinstall hook runs the package installer, and matching-version platform binaries are declared as optional dependencies.
- The fallback fetches the requested package version from the npm registry and extracts the platform binary at a fixed archive path.
- The installer links the selected binary to the droid command shim as an optimization.
Evidence against
- The fallback downloads a native executable without checking a content hash, though it requests the matching package version from the registry.
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.241.0.
See all versions of @factory/cli for other recorded verdicts.
- Review the evidence and your use of @factory/cli@0.241.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.