@fastify/redis
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:redux | AI (typosquat): @fastify/redis is the official Fastify Redis plugin; no relation to redux — Levenshtein match is coincidental. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 8.0.0 | 2 / 8 | |
| 7.2.0 | 2 / 8 | |
| 7.1.0 | 2 / 8 | |
| 7.0.2 | 2 / 9 | |
| 7.0.1 | 2 / 8 | |
| 7.0.0 | 2 / 8 |
v7.0.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (fdawgs) than the most recent previously approved version (matteo.collina) on 2025-01-10, but fdawgs is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v7.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.