@byu-oit-sdk/jwt
JSON Web Token validation for the BYU OIT SDK
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:jest | AI (typosquat): Scoped BYU OIT SDK package for JWT; name similarity to jest is coincidental. | ai | |
| typosquat | typosquat.levenshtein:got | AI (typosquat): Scoped BYU OIT SDK package; not a squatter on got. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped BYU OIT SDK package; not a squatter on joi. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 0.4.0 | 3 / 14 | |
| 0.3.1 | 3 / 14 | |
| 0.3.0 | 3 / 14 | |
| 0.2.0 | 4 / 12 | |
| 0.1.22 | 4 / 12 | |
| 0.1.21 | 4 / 12 | |
| 0.1.20 | 4 / 12 | |
| 0.1.19 | 4 / 12 | |
| 0.1.18 | 4 / 12 | |
| 0.1.17 | 4 / 12 | |
| 0.1.16 | 4 / 12 | |
| 0.1.15 | 4 / 12 | |
| 0.1.14 | 4 / 12 | |
| 0.1.13 | 4 / 12 | |
| 0.1.12 | 4 / 12 | |
| 0.1.11 | 4 / 12 | |
| 0.1.10 | 4 / 12 | |
| 0.1.9 | 4 / 12 | |
| 0.1.8 | 4 / 12 | |
| 0.1.7 | 4 / 12 | |
| 0.1.6 | 4 / 12 | |
| 0.1.4 | 4 / 12 | |
| 0.1.3 | 4 / 12 |
v0.1.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.