@types/express
TypeScript definitions for Express
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 |
|---|---|---|---|---|
| email-domain | unclaimed-email:https://github.com/borisyankov/ | AI (email-domain): The 'email' field contains a GitHub profile URL, not an actual email address. This is a metadata quirk in an old package; no real domain hijacking risk exists as github.com is not unclaimed. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @types/express routinely adds @types/* deps as Express's type surface evolves; @types/qs is a legitimate DefinitelyTyped package for Express's query string parsing dependency. | ai | |
| phantom-deps | phantom-dep:@types/body-parser | AI (phantom-deps): @types/* packages declare type dependencies that are referenced in .d.ts files, not via runtime imports. Phantom-dep findings are expected and benign for all DefinitelyTyped packages. | ai | |
| phantom-deps | phantom-dep:@types/serve-static | AI (phantom-deps): @types/* packages declare type dependencies that are referenced in .d.ts files, not via runtime imports. Phantom-dep findings are expected and benign for all DefinitelyTyped packages. | ai | |
| phantom-deps | phantom-dep:@types/express-serve-static-core | AI (phantom-deps): @types/* packages declare type dependencies that are referenced in .d.ts files, not via runtime imports. Phantom-dep findings are expected and benign for all DefinitelyTyped packages. | ai | |
| dependencies | unvetted-dep:@types/qs | AI (dependencies): @types/qs is a standard DefinitelyTyped package for the qs library, a legitimate and expected type dependency for @types/express. | ai | |
| provenance | no-provenance | AI (provenance): Package predates widespread provenance adoption; published by the trusted DefinitelyTyped/types publisher with a long clean track record. | ai | |
| phantom-deps | phantom-dep:@types/qs | AI (phantom-deps): @types/* packages declare type dependencies that are referenced in .d.ts files, not via runtime imports. Phantom-dep findings are expected and benign for all DefinitelyTyped packages. | ai |
Versions (showing 47 of 47)
| Version | Deps | Published |
|---|---|---|
| 5.0.6 | 3 / 0 | |
| 5.0.5 | 3 / 0 | |
| 5.0.4 | 3 / 0 | |
| 5.0.3 | 3 / 0 | |
| 5.0.2 | 3 / 0 | |
| 5.0.1 | 3 / 0 | |
| 5.0.0 | 4 / 0 | |
| 4.17.25 | 4 / 0 | |
| 4.17.24 | 4 / 0 | |
| 4.17.23 | 4 / 0 | |
| 4.17.22 | 4 / 0 | |
| 4.17.21 | 4 / 0 | |
| 4.17.20 | 4 / 0 | |
| 4.17.19 | 4 / 0 | |
| 4.17.18 | 4 / 0 | |
| 4.17.17 | 4 / 0 | |
| 4.17.16 | 4 / 0 | |
| 4.17.15 | 4 / 0 | |
| 4.17.14 | 4 / 0 | |
| 4.17.13 | 4 / 0 | |
| 4.17.12 | 4 / 0 | |
| 4.17.11 | 4 / 0 | |
| 4.17.10 | 4 / 0 | |
| 4.17.9 | 4 / 0 | |
| 4.17.8 | 4 / 0 | |
| 4.17.7 | 4 / 0 | |
| 4.17.6 | 4 / 0 | |
| 4.17.5 | 4 / 0 | |
| 4.17.4 | 4 / 0 | |
| 4.17.3 | 3 / 0 | |
| 4.17.2 | 3 / 0 | |
| 4.17.1 | 3 / 0 | |
| 4.17.0 | 3 / 0 | |
| 4.16.1 | 3 / 0 | |
| 4.16.0 | 3 / 0 | |
| 4.11.1 | 3 / 0 | |
| 4.11.0 | 3 / 0 | |
| 4.0.39 | 3 / 0 | |
| 4.0.38 | 3 / 0 | |
| 4.0.37 | 2 / 0 | |
| 4.0.36 | 2 / 0 | |
| 4.0.35 | 2 / 0 | |
| 4.0.34 | 2 / 0 | |
| 4.0.33 | 2 / 0 | |
| 4.0.32 | 2 / 0 | |
| 4.0.31 | 2 / 0 | |
| 4.0.29 | 2 / 0 |
v5.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.17.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.17.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.17.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.17.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.17.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.17.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.17.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.17.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.17.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.17.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.17.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.17.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.17.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.17.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.17.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.17.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.17.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.17.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.17.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.17.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.