@fastify/jwt
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:jest | AI (typosquat): @fastify/jwt is an official Fastify-scoped package for JWT handling; Levenshtein proximity to 'jest' is a false positive with no impersonation intent. | ai | |
| typosquat | typosquat.levenshtein:got | AI (typosquat): @fastify/jwt is an official Fastify-scoped package; Levenshtein proximity to 'got' is a false positive with no impersonation intent. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): @fastify/jwt is an official Fastify-scoped package; Levenshtein proximity to 'joi' is a false positive with no impersonation intent. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 usage is in TypeScript type-definition test fixtures demonstrating secret callback signatures; no runtime payload or malicious intent. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 10.2.1 | 5 / 8 | |
| 10.2.0 | 5 / 8 | |
| 10.1.0 | 5 / 8 | |
| 10.0.0 | 5 / 8 |
v10.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.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 (eomm) than the most recent previously approved version (matteo.collina) on 2026-07-08, but eomm 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.