@midwayjs/jwt
midway jwt component
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): Scoped @midwayjs/jwt is a legitimate JWT component, not a typosquat of jest. | ai | |
| typosquat | typosquat.levenshtein:got | AI (typosquat): Scoped @midwayjs/jwt is a legitimate JWT component, not a typosquat of got. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped @midwayjs/jwt is a legitimate JWT component, not a typosquat of joi. | ai | |
| phantom-deps | phantom-dep:@types/jsonwebtoken | AI (phantom-deps): @types/jsonwebtoken is a type-only dependency used for TypeScript declarations, not a runtime import. | ai |
Versions (showing 51 of 144)
| Version | Deps | Published |
|---|---|---|
| 4.1.0 | 2 / 5 | |
| 4.0.3 | 2 / 5 | |
| 4.0.2 | 2 / 5 | |
| 4.0.1 | 2 / 5 | |
| 4.0.0 | 2 / 5 | |
| 3.20.24 | 2 / 5 | |
| 3.20.23 | 2 / 5 | |
| 3.20.22 | 2 / 5 | |
| 3.20.19 | 2 / 5 | |
| 3.20.16 | 2 / 5 | |
| 3.20.15 | 2 / 5 | |
| 3.20.13 | 2 / 5 | |
| 3.20.12 | 2 / 5 | |
| 3.20.11 | 2 / 5 | |
| 3.20.9 | 2 / 5 | |
| 3.20.5 | 2 / 5 | |
| 3.20.4 | 2 / 5 | |
| 3.20.3 | 2 / 5 | |
| 3.20.2 | 2 / 5 | |
| 3.20.0 | 2 / 5 | |
| 3.19.3 | 2 / 5 | |
| 3.19.2 | 2 / 5 | |
| 3.19.0 | 2 / 5 | |
| 3.18.2 | 2 / 5 | |
| 3.18.0 | 2 / 5 | |
| 3.17.3 | 2 / 5 | |
| 3.17.1 | 2 / 5 | |
| 3.17.0 | 2 / 5 | |
| 3.16.8 | 2 / 5 | |
| 3.16.6 | 2 / 5 | |
| 3.16.5 | 2 / 5 | |
| 3.16.4 | 2 / 5 | |
| 3.16.2 | 2 / 5 | |
| 3.16.1 | 2 / 5 | |
| 3.16.0 | 2 / 5 | |
| 3.15.11 | 2 / 5 | |
| 3.15.10 | 2 / 5 | |
| 3.15.8 | 2 / 5 | |
| 3.15.7 | 2 / 5 | |
| 3.15.6 | 2 / 5 | |
| 3.15.2 | 2 / 5 | |
| 3.15.1 | 2 / 5 | |
| 3.15.0 | 2 / 5 | |
| 3.14.12 | 2 / 5 | |
| 3.14.11 | 2 / 5 | |
| 3.14.10 | 2 / 5 | |
| 3.14.7 | 2 / 5 | |
| 3.14.4 | 2 / 5 | |
| 3.14.3 | 2 / 5 | |
| 3.14.0 | 2 / 5 | |
| 3.13.9 | 2 / 5 |
v3.20.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.20.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.20.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.19.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.19.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.18.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.15.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.