@firestitch/standards
Firestitch engineering standards - routing indexes and rule documents
This report shows the evidence for @firestitch/standards@1.0.2. 2 of 2 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThe lifecycle hook performs concrete, persistent AI-agent instruction-file mutation outside the package directory. Absence of exfiltration does not remove this install-time control-surface risk.
Decision evidence
public snapshot- package.json runs postinstall on npm install.
- bin/postinstall.js finds consuming repo root via .git.
- bin/postinstall.js overwrites consuming repo CLAUDE.md.
- Hook creates CLAUDE.local.md and modifies .gitignore.
- Generated CLAUDE.md imposes instructions on AI-agent work.
- No network, credential harvesting, shell execution, or remote payload loading found.
- Only executable package file is bin/postinstall.js; remaining files are standards documents.
Source & flagged code
2 flagged · loading sourcePackage 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 @firestitch/standards@1.0.2.
The versions list below shows the verdict for each recorded version.
- Avoid installing @firestitch/standards@1.0.2. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.