3a-factory@4.2.2
Enterprise Feature-local Spec Package workflow for Claude, Gemini, and Cursor (3A-Factory)
AI Security Review
scanned 22d ago · by lpm-firewall-aiThe source prevents unconsented npm lifecycle mutation but exposes explicit-command agent control-surface writes. Under the supplied policy, this warrants a warning rather than publication blocking.
Decision evidence
public snapshot- Explicit invocation writes Claude commands, Gemini commands, and Cursor rules into the selected project.
- The installer also installs AGENTS.md and shared agent configuration.
- npm postinstall invokes the installer, but its lifecycle guard exits before project scaffolding.
- Existing differing files are skipped unless force is enabled; forced updates receive backups by default.
- No credential harvesting, network requests, remote payload execution, or runtime self-dependency was identified in the inspected installer.
- Automatic npm lifecycle execution does not perform the agent configuration writes.
Source & flagged code
6 flagged · loading sourceInstall-time lifecycle script matches a deterministic static-gate block pattern.
package.jsonView on unpkgPackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to 3a-factory@4.2.2.
See all versions of 3a-factory for other recorded verdicts.
- Review the evidence and your use of 3a-factory@4.2.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.