@factory/cli@0.208.2
Factory Droid CLI - AI-powered software engineering agent
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe automatic native-binary setup is a supply-chain-sensitive capability, but source confines it to fixed same-vendor platform packages and package-local files. No source evidence shows secret theft, broad persistence, destructive action, or remote code selection beyond the version-matched npm binary fallback.
Decision evidence
public snapshot- The manifest automatically runs install.js after installation.
- If an optional platform package is missing, the installer downloads its matching npm package and writes its droid binary locally.
- On Unix, the installer replaces the package's droid shim with a hard link or symlink to that binary.
- The download is limited to version-matched @factory platform packages selected from a fixed platform map.
- NPM_TOKEN is attached only to requests whose host includes npmjs.org; the source contains no credential collection or exfiltration.
- The installer only changes its own bin/droid path and prints PATH guidance; it does not modify shell profiles or project files.
Source & flagged code
7 flaggedPackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-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 · L9Install-time lifecycle script is not statically allowlisted and needs review.
Findings
Affected versions and remediation
This report applies to @factory/cli@0.208.2.
See all versions of @factory/cli for other recorded verdicts.
- Review the evidence and your use of @factory/cli@0.208.2 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.