@factory/cli@0.205.0
Factory Droid CLI - AI-powered software engineering agent
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe postinstall behavior is a package-local binary shim for the Factory Droid CLI, with registry downloads limited to the matching platform package and the npm token bound to npmjs.org hosts. No credential harvesting, agent-control writes, or self-install chain appears in the inspected sources.
Decision evidence
public snapshot- postinstall runs node install.js to select the matching platform binary and replace the local droid shim with a link to it.
- If the optional platform package is missing, install fetches that same-version package tarball from registry.npmjs.org and extracts package/bin/droid into this package bin directory.
- NPM_TOKEN is added only when the request host includes npmjs.org.
- The global-install PATH check only prints a suggested shell command and does not write profile or agent config files.
- Optional dependencies are same-version @factory platform packages, not another release of @factory/cli.
Source & flagged code
6 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.205.0.
See all versions of @factory/cli for other recorded verdicts.
- Review the evidence and your use of @factory/cli@0.205.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.