registry / @factory/cli / 0.197.0
@factory/cli@0.197.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 from npm and is scoped to this package's executable. Source inspection found no credential harvesting, exfiltration, destructive action, or AI-agent control-surface mutation.
Static reason
One or more suspicious static signals were detected.
Trigger
npm postinstall when the platform optional dependency is unavailable; user invocation of droid
Impact
Installs and invokes the intended platform CLI binary; no confirmed exfiltration, persistence, or foreign configuration mutation.
Mechanism
package-local native CLI bootstrap and shim optimization
AI rationale
The lifecycle behavior is package-aligned native CLI installation from npm and is scoped to this package's executable. Source inspection found no credential harvesting, exfiltration, destructive action, or AI-agent control-surface mutation.
Evidence
package.jsoninstall.jsplatform.jsbin/droidbin/droid.backupbin/droid.exe
Network endpoints1
registry.npmjs.org/
Decision evidence
public snapshotAI called this Clean at 90.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- Postinstall can fetch a versioned platform tarball from npm when its optional dependency is absent.
- The fallback writes a native binary inside its own bin directory; Unix then relinks only its own shim.
Evidence against
- Registry lookup is restricted to the selected @factory platform package and this package version.
- NPM_TOKEN is attached only for an npmjs.org hostname, not collected or sent elsewhere.
- No source writes agent configuration, shell profiles, credentials, or paths outside the package.
- The CLI shim executes the selected binary only when the user runs droid.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetworkShell
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
HighShellinstall.js
HighSame File Env Network Executioninstall.js#virtual:normalized:round1
HighUnverified Remote Native Payload Installpackage.json
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.197.0.
See all versions of @factory/cli for other recorded verdicts.
- Review the evidence and your use of @factory/cli@0.197.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.