@fastify/sse
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 |
|---|---|---|---|---|
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): 127.0.0.1 reference is in a benchmark file connecting to localhost; not a real external IP. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped @fastify/ package; Levenshtein match to 'qs' is a false positive for this namespace. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.6.0 | 2 / 8 | |
| 0.5.0 | 2 / 8 | |
| 0.4.0 | 1 / 7 | |
| 0.3.0 | 1 / 7 | |
| 0.2.0 | 1 / 6 | |
| 0.1.0 | 1 / 6 |
v0.6.0
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 (climba03003) than the most recent previously approved version (kibertoad) on 2026-07-27, but climba03003 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.
v0.5.0
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 (kibertoad) than the most recent previously approved version (matteo.collina) on 2026-07-01, but kibertoad 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.