@verii/jwt
Set of JWT related functions used in Verii projects
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:jest | AI (typosquat): @verii/jwt is a scoped JWT library from LFDT-Verii org; Levenshtein match to 'jest' is a false positive with no semantic or visual similarity. | ai | |
| typosquat | typosquat.levenshtein:got | AI (typosquat): @verii/jwt is a scoped JWT library from LFDT-Verii org; Levenshtein match to 'got' is a false positive with no semantic or visual similarity. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): @verii/jwt is a scoped JWT library from LFDT-Verii org; Levenshtein match to 'joi' is a false positive with no semantic or visual similarity. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decoding in core.js is standard JWT payload parsing — expected and benign for a JWT library. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decoding in key-transformer.js is standard cryptographic key format conversion — expected and benign for a JWT/crypto library. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 1.1.3 | 5 / 15 | |
| 1.1.2 | 5 / 15 | |
| 1.1.1 | 5 / 15 | |
| 1.1.0 | 5 / 15 | |
| 1.0.9 | 6 / 14 | |
| 1.0.8 | 6 / 14 | |
| 1.0.7 | 6 / 14 | |
| 1.0.6 | 6 / 14 | |
| 1.0.5 | 6 / 14 | |
| 1.0.4 | 6 / 14 | |
| 1.0.3 | 6 / 14 | |
| 1.0.2 | 6 / 14 | |
| 1.0.1 | 6 / 14 | |
| 1.0.0 | 6 / 14 |
v1.1.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.