@box/combobox-with-api
<!-- START doctoc generated TOC please keep comment here to allow auto update --> <!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->
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
Versions (showing 100 of 345)
| Version | Deps | Published |
|---|---|---|
| 1.42.30 | 2 / 5 | |
| 1.42.29 | 2 / 5 | |
| 1.42.28 | 2 / 5 | |
| 1.42.27 | 2 / 5 | |
| 1.42.26 | 2 / 5 | |
| 1.42.25 | 2 / 5 | |
| 1.42.24 | 2 / 5 | |
| 1.42.23 | 2 / 5 | |
| 1.42.22 | 2 / 5 | |
| 1.42.21 | 2 / 5 | |
| 1.42.20 | 2 / 5 | |
| 1.42.19 | 2 / 5 | |
| 1.42.18 | 2 / 5 | |
| 1.42.17 | 2 / 5 | |
| 1.42.16 | 2 / 5 | |
| 1.42.15 | 2 / 5 | |
| 1.42.14 | 2 / 5 | |
| 1.42.13 | 2 / 5 | |
| 1.42.12 | 2 / 5 | |
| 1.42.11 | 2 / 5 | |
| 1.42.10 | 2 / 5 | |
| 1.42.9 | 2 / 5 | |
| 1.42.8 | 2 / 5 | |
| 1.42.7 | 2 / 5 | |
| 1.42.6 | 2 / 5 | |
| 1.42.5 | 2 / 5 | |
| 1.42.4 | 2 / 5 | |
| 1.42.3 | 2 / 5 | |
| 1.42.2 | 2 / 5 | |
| 1.42.1 | 2 / 5 | |
| 1.42.0 | 2 / 5 | |
| 1.41.44 | 2 / 5 | |
| 1.41.43 | 2 / 5 | |
| 1.41.42 | 2 / 5 | |
| 1.41.41 | 2 / 5 | |
| 1.41.40 | 2 / 5 | |
| 1.41.39 | 2 / 5 | |
| 1.41.38 | 2 / 5 | |
| 1.41.37 | 2 / 5 | |
| 1.41.36 | 2 / 5 | |
| 1.41.35 | 2 / 5 | |
| 1.41.34 | 2 / 5 | |
| 1.41.33 | 2 / 5 | |
| 1.41.32 | 2 / 5 | |
| 1.41.31 | 2 / 5 | |
| 1.41.30 | 2 / 5 | |
| 1.41.29 | 2 / 5 | |
| 1.41.28 | 2 / 5 | |
| 1.41.27 | 2 / 5 | |
| 1.41.26 | 2 / 5 | |
| 1.41.25 | 2 / 5 | |
| 1.41.24 | 2 / 5 | |
| 1.41.23 | 2 / 5 | |
| 1.41.22 | 2 / 5 | |
| 1.41.21 | 2 / 5 | |
| 1.41.20 | 2 / 5 | |
| 1.41.19 | 2 / 5 | |
| 1.41.18 | 2 / 5 | |
| 1.41.17 | 2 / 5 | |
| 1.41.16 | 2 / 5 | |
| 1.41.15 | 2 / 5 | |
| 1.41.14 | 2 / 5 | |
| 1.41.13 | 2 / 5 | |
| 1.41.12 | 2 / 5 | |
| 1.41.11 | 2 / 5 | |
| 1.41.10 | 2 / 5 | |
| 1.41.9 | 2 / 5 | |
| 1.41.8 | 2 / 5 | |
| 1.41.7 | 2 / 5 | |
| 1.41.6 | 2 / 5 | |
| 1.41.5 | 2 / 5 | |
| 1.41.4 | 2 / 5 | |
| 1.41.3 | 2 / 5 | |
| 1.41.2 | 2 / 5 | |
| 1.41.1 | 2 / 5 | |
| 1.41.0 | 2 / 5 | |
| 1.40.1 | 2 / 5 | |
| 1.40.0 | 2 / 5 | |
| 1.39.2 | 2 / 5 | |
| 1.39.1 | 2 / 5 | |
| 1.39.0 | 2 / 5 | |
| 1.38.2 | 2 / 5 | |
| 1.38.1 | 2 / 5 | |
| 1.38.0 | 2 / 5 | |
| 1.37.1 | 2 / 5 | |
| 1.37.0 | 2 / 5 | |
| 1.36.0 | 2 / 5 | |
| 1.35.0 | 2 / 5 | |
| 1.34.2 | 2 / 5 | |
| 1.34.1 | 2 / 5 | |
| 1.34.0 | 2 / 5 | |
| 1.33.2 | 2 / 5 | |
| 1.33.1 | 2 / 5 | |
| 1.33.0 | 2 / 5 | |
| 1.32.4 | 2 / 5 | |
| 1.32.3 | 2 / 5 | |
| 1.32.2 | 2 / 5 | |
| 1.32.1 | 2 / 5 | |
| 1.32.0 | 2 / 5 | |
| 1.31.0 | 2 / 5 |
v1.42.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.42.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.42.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.41.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.41.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.41.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.41.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.41.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.41.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.41.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.41.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.41.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.41.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.41.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.41.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.41.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.41.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.41.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.41.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.41.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.41.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.41.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.41.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.41.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.41.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.41.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.41.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.41.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.41.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.41.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.41.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.41.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.41.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.41.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.41.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.41.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.41.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.41.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.41.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.41.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.41.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.41.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.41.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.41.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.41.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.41.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.41.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.41.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.40.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.40.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.39.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.39.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.39.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.38.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.38.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.38.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.36.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.35.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.34.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.34.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.34.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.33.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.33.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.33.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.32.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.32.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.32.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.32.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.32.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.