@fastify/jwt — Greenflagged

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

simonebdelvedormatteo.collinajsumnerszektheommfox1tairhornskibertoadclimba03003galvezsimenbgurgundaytony133metcoder95jean-micheletilteooodfdawgs

Keywords

jwtjsontokenjsonwebtokenfastify

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	2026/04/27
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	2026/04/27
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	2026/04/27
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	2026/04/27

Versions (showing 2 of 2)

Version	Deps	Published
10.1.0	5 / 8	2026-05-18
10.0.0	5 / 8	2025-08-13

v10.1.0

2 findings

HIGH Publisher changed: kibertoad → matteo.collina (on 2026-05-18) provenance

This version was published by a different npm account than previous versions on 2026-05-18. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.