@weapon/redact
Sensitive field redaction [weapon](https://github.com/sigitex/weapon).
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:react | AI (typosquat): Scoped package @weapon/redact in sigitex monorepo; Levenshtein match to 'react' is coincidental, not impersonation. | ai | |
| phantom-deps | phantom-dep:regexparam | AI (phantom-deps): regexparam is declared as a runtime dep via pnpm catalog syntax; phantom-dep heuristic doesn't resolve catalog: references. | ai |
v1.0.2
2 findingsPackage name '@weapon/redact' is 1 edit(s) away from popular package 'react'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
2 findingsPackage name '@weapon/redact' is 1 edit(s) away from popular package 'react'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
2 findingsPackage name '@weapon/redact' is 1 edit(s) away from popular package 'react'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.