bun-types
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): bun-types declares @types/node as a peer/transitive type dep for consumers; not directly imported by design. Standard for type packages. | ai |
Versions (showing 100 of 117)
| Version | Deps | Published |
|---|---|---|
| 1.3.14 | 1 / 0 | |
| 1.3.13 | 1 / 0 | |
| 1.3.12 | 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 / 1 | |
| 1.3.1 | 1 / 1 | |
| 1.3.0 | 1 / 1 | |
| 1.2.23 | 1 / 1 | |
| 1.2.22 | 1 / 1 | |
| 1.2.21 | 1 / 1 | |
| 1.2.20 | 1 / 1 | |
| 1.2.19 | 1 / 2 | |
| 1.2.18 | 1 / 2 | |
| 1.2.17 | 1 / 1 | |
| 1.2.16 | 1 / 1 | |
| 1.2.15 | 1 / 1 | |
| 1.2.14 | 1 / 1 | |
| 1.2.13 | 1 / 4 | |
| 1.2.12 | 1 / 4 | |
| 1.2.11 | 1 / 4 | |
| 1.2.10 | 1 / 4 | |
| 1.2.9 | 2 / 4 | |
| 1.2.8 | 2 / 4 | |
| 1.2.7 | 2 / 4 | |
| 1.2.6 | 2 / 4 | |
| 1.2.5 | 2 / 4 | |
| 1.2.4 | 2 / 4 | |
| 1.2.3 | 2 / 4 | |
| 1.2.2 | 2 / 4 | |
| 1.2.1 | 2 / 4 | |
| 1.2.0 | 2 / 4 | |
| 1.1.45 | 2 / 4 | |
| 1.1.44 | 2 / 4 | |
| 1.1.43 | 2 / 4 | |
| 1.1.42 | 2 / 4 | |
| 1.1.41 | 2 / 4 | |
| 1.1.40 | 2 / 4 | |
| 1.1.39 | 2 / 4 | |
| 1.1.38 | 2 / 4 | |
| 1.1.37 | 2 / 4 | |
| 1.1.36 | 2 / 4 | |
| 1.1.35 | 2 / 4 | |
| 1.1.34 | 2 / 4 | |
| 1.1.33 | 2 / 4 | |
| 1.1.32 | 2 / 4 | |
| 1.1.31 | 2 / 4 | |
| 1.1.30 | 2 / 4 | |
| 1.1.29 | 2 / 4 | |
| 1.1.28 | 2 / 4 | |
| 1.1.27 | 2 / 4 | |
| 1.1.26 | 2 / 4 | |
| 1.1.25 | 2 / 4 | |
| 1.1.24 | 2 / 4 | |
| 1.1.23 | 2 / 4 | |
| 1.1.22 | 2 / 4 | |
| 1.1.21 | 2 / 4 | |
| 1.1.20 | 2 / 4 | |
| 1.1.19 | 2 / 4 | |
| 1.1.18 | 2 / 4 | |
| 1.1.17 | 2 / 4 | |
| 1.1.16 | 2 / 4 | |
| 1.1.15 | 2 / 4 | |
| 1.1.14 | 2 / 4 | |
| 1.1.13 | 2 / 4 | |
| 1.1.12 | 2 / 4 | |
| 1.1.11 | 2 / 4 | |
| 1.1.10 | 2 / 4 | |
| 1.1.9 | 2 / 4 | |
| 1.1.8 | 2 / 4 | |
| 1.1.7 | 2 / 4 | |
| 1.1.6 | 2 / 4 | |
| 1.1.5 | 2 / 4 | |
| 1.1.4 | 2 / 4 | |
| 1.1.3 | 2 / 4 | |
| 1.1.2 | 2 / 4 | |
| 1.1.1 | 2 / 4 | |
| 1.1.0 | 2 / 4 | |
| 1.0.36 | 2 / 4 | |
| 1.0.35 | 2 / 4 | |
| 1.0.34 | 2 / 4 | |
| 1.0.33 | 2 / 4 | |
| 1.0.32 | 2 / 4 | |
| 1.0.31 | 2 / 4 | |
| 1.0.30 | 2 / 4 | |
| 1.0.29 | 2 / 4 | |
| 1.0.28 | 2 / 4 | |
| 1.0.27 | 2 / 4 | |
| 1.0.26 | 2 / 4 | |
| 1.0.25 | 3 / 0 | |
| 1.0.24 | 3 / 0 | |
| 1.0.23 | 3 / 0 | |
| 1.0.22 | 3 / 0 | |
| 1.0.21 | 3 / 0 | |
| 1.0.20 | 3 / 0 | |
| 1.0.19 | 3 / 0 | |
| 1.0.18 | 0 / 0 | |
| 1.0.17 | 0 / 0 |
v1.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.