@box/user-selector
<!-- 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 392)
| Version | Deps | Published |
|---|---|---|
| 1.74.30 | 0 / 8 | |
| 1.74.29 | 0 / 8 | |
| 1.74.28 | 0 / 8 | |
| 1.74.27 | 0 / 8 | |
| 1.74.26 | 0 / 8 | |
| 1.74.25 | 0 / 8 | |
| 1.74.24 | 0 / 8 | |
| 1.74.23 | 0 / 8 | |
| 1.74.22 | 0 / 8 | |
| 1.74.21 | 0 / 8 | |
| 1.74.20 | 0 / 8 | |
| 1.74.19 | 0 / 8 | |
| 1.74.18 | 0 / 8 | |
| 1.74.17 | 0 / 8 | |
| 1.74.16 | 0 / 8 | |
| 1.74.15 | 0 / 8 | |
| 1.74.14 | 0 / 8 | |
| 1.74.13 | 0 / 8 | |
| 1.74.12 | 0 / 8 | |
| 1.74.11 | 0 / 8 | |
| 1.74.10 | 0 / 8 | |
| 1.74.9 | 0 / 8 | |
| 1.74.8 | 0 / 8 | |
| 1.74.7 | 0 / 8 | |
| 1.74.6 | 0 / 8 | |
| 1.74.5 | 0 / 8 | |
| 1.74.4 | 0 / 8 | |
| 1.74.3 | 0 / 8 | |
| 1.74.2 | 0 / 8 | |
| 1.74.1 | 0 / 8 | |
| 1.74.0 | 0 / 8 | |
| 1.73.44 | 0 / 8 | |
| 1.73.43 | 0 / 8 | |
| 1.73.42 | 0 / 8 | |
| 1.73.41 | 0 / 8 | |
| 1.73.40 | 0 / 8 | |
| 1.73.39 | 0 / 8 | |
| 1.73.38 | 0 / 8 | |
| 1.73.37 | 0 / 8 | |
| 1.73.36 | 0 / 8 | |
| 1.73.35 | 0 / 8 | |
| 1.73.34 | 0 / 8 | |
| 1.73.33 | 0 / 8 | |
| 1.73.32 | 0 / 8 | |
| 1.73.31 | 0 / 8 | |
| 1.73.30 | 0 / 8 | |
| 1.73.29 | 0 / 8 | |
| 1.73.28 | 0 / 8 | |
| 1.73.27 | 0 / 8 | |
| 1.73.26 | 0 / 8 | |
| 1.73.25 | 0 / 8 | |
| 1.73.24 | 0 / 8 | |
| 1.73.23 | 0 / 8 | |
| 1.73.22 | 0 / 8 | |
| 1.73.21 | 0 / 8 | |
| 1.73.20 | 0 / 8 | |
| 1.73.19 | 0 / 8 | |
| 1.73.18 | 0 / 8 | |
| 1.73.17 | 0 / 8 | |
| 1.73.16 | 0 / 8 | |
| 1.73.15 | 0 / 8 | |
| 1.73.14 | 0 / 8 | |
| 1.73.13 | 0 / 8 | |
| 1.73.12 | 0 / 8 | |
| 1.73.11 | 0 / 8 | |
| 1.73.10 | 0 / 8 | |
| 1.73.9 | 0 / 8 | |
| 1.73.8 | 0 / 8 | |
| 1.73.7 | 0 / 8 | |
| 1.73.6 | 0 / 8 | |
| 1.73.5 | 0 / 8 | |
| 1.73.4 | 0 / 8 | |
| 1.73.3 | 0 / 8 | |
| 1.73.2 | 0 / 8 | |
| 1.73.1 | 0 / 8 | |
| 1.73.0 | 0 / 8 | |
| 1.72.1 | 0 / 8 | |
| 1.72.0 | 0 / 8 | |
| 1.71.2 | 0 / 8 | |
| 1.71.1 | 0 / 8 | |
| 1.71.0 | 0 / 8 | |
| 1.70.2 | 0 / 8 | |
| 1.70.1 | 0 / 8 | |
| 1.70.0 | 0 / 8 | |
| 1.69.0 | 0 / 8 | |
| 1.68.2 | 0 / 8 | |
| 1.68.1 | 0 / 8 | |
| 1.68.0 | 0 / 8 | |
| 1.67.0 | 0 / 8 | |
| 1.66.2 | 0 / 8 | |
| 1.66.1 | 0 / 8 | |
| 1.66.0 | 0 / 8 | |
| 1.65.2 | 0 / 8 | |
| 1.65.1 | 0 / 8 | |
| 1.65.0 | 0 / 8 | |
| 1.64.0 | 0 / 8 | |
| 1.63.3 | 0 / 8 | |
| 1.63.2 | 0 / 8 | |
| 1.63.1 | 0 / 8 | |
| 1.63.0 | 0 / 8 |
v1.74.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.74.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.74.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.73.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.73.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.73.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.73.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.73.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.73.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.73.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.73.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.73.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.73.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.73.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.73.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.73.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.73.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.73.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.73.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.73.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.73.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.73.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.73.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.73.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.73.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.73.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.73.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.73.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.73.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.73.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.73.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.73.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.73.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.73.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.73.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.73.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.73.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.73.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.73.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.73.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.73.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.73.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.73.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.73.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.73.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.73.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.73.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.73.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.72.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.72.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.71.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.71.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.71.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.70.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.70.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.70.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.69.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.68.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.68.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.68.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.67.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.66.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.66.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.66.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.65.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.65.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.65.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.64.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.63.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.63.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.63.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.63.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.