3a-factory@4.2.1
⚠ Under reviewEnterprise Feature-local Spec Package workflow for Claude, Gemini, and Cursor (3A-Factory)
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThis is a real explicit-user agent configuration installer, not malicious install-time behavior. Its lifecycle guard prevents consumer-project mutation during npm installation, so a warning is appropriate rather than a block.
Decision evidence
public snapshot- Explicit CLI execution writes shared agent instructions, skills, commands, and Cursor rules into the selected project.
- The installer can overwrite existing project files when the user supplies --force.
- The packaged templates include agent workflow and delegation controls, so this is an agent-configuration capability.
- The postinstall hook detects npm lifecycle execution and exits before scaffolding a consumer project.
- No network, credential collection, shell execution, remote payload loading, or self-dependency is present in the inspected runtime source.
- Normal writes avoid differing existing files unless the user explicitly supplies --force.
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.1.
See all versions of 3a-factory for other recorded verdicts.
- Review the evidence and your use of 3a-factory@4.2.1 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.