registry / @factory/cli / 0.218.0
@factory/cli@0.218.0
Factory Droid CLI - AI-powered software engineering agent
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe lifecycle hook performs a package-aligned native CLI installation fallback and rewrites only its own command shim. Source inspection found no self-dependency chain, secret exfiltration, broad persistence, or AI-agent control-surface mutation.
Static reason
One or more suspicious static signals were detected.
Trigger
npm postinstall, or a later user invocation of droid.
Impact
The package can install and run its own platform-specific CLI binary; no unauthorized data collection or external control-surface modification is shown.
Mechanism
Platform binary selection with a registry fallback and local shim optimization.
AI rationale
The lifecycle hook performs a package-aligned native CLI installation fallback and rewrites only its own command shim. Source inspection found no self-dependency chain, secret exfiltration, broad persistence, or AI-agent control-surface mutation.
Decision evidence
public snapshotAI called this Clean at 88.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- A postinstall hook can fetch an exact-version platform binary from the npm registry fallback and write it executable.
- The hook replaces only its own droid shim with a link to the selected platform binary.
Evidence against
- Platform packages are fixed, same-vendor optional dependencies at version 0.218.0; there is no runtime dependency on this package itself.
- The network fallback is limited to npm registry package retrieval, and no credential harvesting, exfiltration, agent-config modification, or project-wide mutation is present.
- The command shim executes the selected platform binary only when the user invokes droid.
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.218.0.
See all versions of @factory/cli for other recorded verdicts.
- Review the evidence and your use of @factory/cli@0.218.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.