registry / @factory/cli / 0.190.0
@factory/cli@0.190.0
Factory Droid CLI - AI-powered software engineering agent
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThe lifecycle behavior is package-aligned native-CLI installation: fallback retrieval is from the npm registry for declared optional dependencies and writes only the local command shim. Source inspection found no concrete malicious chain.
Static reason
One or more suspicious static signals were detected.
Trigger
npm postinstall; runtime invocation of droid
Impact
Installs or executes the package's platform-specific native CLI binary; no source-confirmed exfiltration or persistence beyond the package-local executable shim.
Mechanism
platform binary selection, npm fallback download, and package-local shim relink
AI rationale
The lifecycle behavior is package-aligned native-CLI installation: fallback retrieval is from the npm registry for declared optional dependencies and writes only the local command shim. Source inspection found no concrete malicious chain.
Evidence
package.jsoninstall.jsplatform.jsbin/droidbin/droid.backup
Network endpoints1
registry.npmjs.org/
Decision evidence
public snapshotAI called this Clean at 89.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json runs postinstall via install.js.
- install.js can fetch a missing platform binary from registry.npmjs.org and write bin/droid.
- postinstall relinks only this package's bin/droid shim to its platform binary.
Evidence against
- Network fallback is restricted to npm registry packument/tarball retrieval for declared @factory platform packages.
- NPM_TOKEN is only attached when the request hostname includes npmjs.org.
- No harvesting, non-registry exfiltration, eval, remote script execution, or foreign config writes found.
- Shell-profile strings are printed as user instructions; install.js does not modify shell profiles.
- platform.js commands only detect CPU AVX2 capability; bin/droid forwards user arguments to the selected binary.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
8 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 High5 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
HighTrigger Reachable Persistenceinstall.js
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumNetwork
MediumEnvironment Vars
MediumInstall Persistenceinstall.js
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
Affected versions and remediation
This report applies to @factory/cli@0.190.0.
See all versions of @factory/cli for other recorded verdicts.
- Review the evidence and your use of @factory/cli@0.190.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.