@factory/cli@0.195.0
Factory Droid CLI - AI-powered software engineering agent
AI Security Review
scanned 3mo ago · by lpm-firewall-aiSource inspection shows a conventional native-CLI installer: it resolves @factory platform packages, falls back to the npm registry, and modifies only its own bin shim. No exfiltration, persistence outside the package, destructive action, or AI-agent control-surface mutation is present.
Decision evidence
public snapshot- Postinstall can fetch a versioned platform binary when its optional dependency is absent.
- The fallback writes that binary only to the package-local bin directory.
- The only fixed registry endpoint is registry.npmjs.org and selected package names are the package's own @factory/cli platform variants.
- Postinstall only replaces the package's droid shim with a link to the selected binary; no user config, credentials, or external files are modified.
- Runtime execution forwards user-supplied CLI arguments to the selected platform binary.
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.195.0.
See all versions of @factory/cli for other recorded verdicts.
- Review the evidence and your use of @factory/cli@0.195.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.