@types/express-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 — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Stub @types redirect packages are only published when the upstream package ships its own types; long dormancy is expected and not a takeover signal for this publisher. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Adding express-jwt as the sole dependency is the correct stub redirect pattern; it replaces the old @types/* deps and is not a supply-chain risk. | ai | |
| bogus-package | bogus-package | AI (bogus-package): All bogus-package signals are expected for a DefinitelyTyped stub: no code, no README instructions, no keywords. The package's entire purpose is a deprecation notice. | ai | |
| phantom-deps | phantom-dep:express-jwt | AI (phantom-deps): Stub packages declare a dep without importing it by design; phantom-dep is a structural false positive for this package type. | ai | |
| phantom-deps | phantom-dep:@types/express-unless | AI (phantom-deps): @types/express-unless is a type-only peer dependency loaded by TypeScript convention. Standard pattern for DefinitelyTyped packages. | ai | |
| provenance | no-provenance | AI (provenance): DefinitelyTyped @types/* packages are published via automated tooling without Sigstore provenance; this is expected and stable for this package. | ai | |
| phantom-deps | phantom-dep:@types/express | AI (phantom-deps): @types/express is a type-only peer dependency loaded by TypeScript convention, not via direct import. This is standard for DefinitelyTyped packages. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 7.4.4 | 1 / 0 | |
| 7.4.3 | 1 / 0 | |
| 7.4.2 | 1 / 0 | |
| 6.0.4 | 2 / 0 | |
| 6.0.3 | 2 / 0 | |
| 6.0.2 | 2 / 0 | |
| 6.0.1 | 2 / 0 | |
| 6.0.0 | 2 / 0 | |
| 0.0.42 | 2 / 0 |
v7.4.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.