@types/bun
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:yup | AI (typosquat): @types/bun is the official DefinitelyTyped package for the Bun runtime, not a typosquat of 'yup'. The name similarity is coincidental and the scoped @types namespace confirms legitimacy. | ai | |
| phantom-deps | phantom-dep:bun-types | AI (phantom-deps): bun-types is a types-only dependency used as a re-export target in a .d.ts file, not a runtime import. This pattern is standard for @types/* packages in DefinitelyTyped. | ai | |
| provenance | no-provenance | AI (provenance): DefinitelyTyped/@types packages are published by the trusted 'types' npm account with a long track record; lack of Sigstore provenance is not a concern here. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 1.3.14 | 1 / 0 | |
| 1.3.13 | 1 / 0 | |
| 1.3.12 | 1 / 0 | |
| 1.3.11 | 1 / 0 | |
| 1.3.10 | 1 / 0 | |
| 1.3.9 | 1 / 0 | |
| 1.3.8 | 1 / 0 | |
| 1.3.7 | 1 / 0 | |
| 1.3.6 | 1 / 0 | |
| 1.3.5 | 1 / 0 | |
| 1.3.4 | 1 / 0 | |
| 1.3.3 | 1 / 0 | |
| 1.3.2 | 1 / 0 | |
| 1.3.1 | 1 / 0 | |
| 1.3.0 | 1 / 0 | |
| 1.2.23 | 1 / 0 | |
| 1.2.22 | 1 / 0 | |
| 1.2.21 | 1 / 0 | |
| 1.2.20 | 1 / 0 | |
| 1.2.19 | 1 / 0 | |
| 1.2.18 | 1 / 0 | |
| 1.2.17 | 1 / 0 | |
| 1.2.16 | 1 / 0 | |
| 1.2.15 | 1 / 0 | |
| 1.2.14 | 1 / 0 | |
| 1.2.13 | 1 / 0 | |
| 1.2.12 | 1 / 0 | |
| 1.2.11 | 1 / 0 |
v1.3.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.