@box/box-ai-agent-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 338)
| Version | Deps | Published |
|---|---|---|
| 1.39.30 | 0 / 8 | |
| 1.39.29 | 0 / 8 | |
| 1.39.28 | 0 / 8 | |
| 1.39.27 | 0 / 8 | |
| 1.39.26 | 0 / 8 | |
| 1.39.25 | 0 / 8 | |
| 1.39.24 | 0 / 8 | |
| 1.39.23 | 0 / 8 | |
| 1.39.22 | 0 / 8 | |
| 1.39.21 | 0 / 8 | |
| 1.39.20 | 0 / 8 | |
| 1.39.19 | 0 / 8 | |
| 1.39.18 | 0 / 8 | |
| 1.39.17 | 0 / 8 | |
| 1.39.16 | 0 / 8 | |
| 1.39.15 | 0 / 8 | |
| 1.39.14 | 0 / 8 | |
| 1.39.13 | 0 / 8 | |
| 1.39.12 | 0 / 8 | |
| 1.39.11 | 0 / 8 | |
| 1.39.10 | 0 / 8 | |
| 1.39.9 | 0 / 8 | |
| 1.39.8 | 0 / 8 | |
| 1.39.7 | 0 / 8 | |
| 1.39.6 | 0 / 8 | |
| 1.39.5 | 0 / 8 | |
| 1.39.4 | 0 / 8 | |
| 1.39.3 | 0 / 8 | |
| 1.39.2 | 0 / 8 | |
| 1.39.1 | 0 / 8 | |
| 1.39.0 | 0 / 8 | |
| 1.38.43 | 0 / 8 | |
| 1.38.42 | 0 / 8 | |
| 1.38.41 | 0 / 8 | |
| 1.38.40 | 0 / 8 | |
| 1.38.39 | 0 / 8 | |
| 1.38.38 | 0 / 8 | |
| 1.38.37 | 0 / 8 | |
| 1.38.36 | 0 / 8 | |
| 1.38.35 | 0 / 8 | |
| 1.38.34 | 0 / 8 | |
| 1.38.33 | 0 / 8 | |
| 1.38.32 | 0 / 8 | |
| 1.38.31 | 0 / 8 | |
| 1.38.30 | 0 / 8 | |
| 1.38.29 | 0 / 8 | |
| 1.38.28 | 0 / 8 | |
| 1.38.27 | 0 / 8 | |
| 1.38.26 | 0 / 8 | |
| 1.38.25 | 0 / 8 | |
| 1.38.24 | 0 / 8 | |
| 1.38.23 | 0 / 8 | |
| 1.38.22 | 0 / 8 | |
| 1.38.21 | 0 / 8 | |
| 1.38.20 | 0 / 8 | |
| 1.38.19 | 0 / 8 | |
| 1.38.18 | 0 / 8 | |
| 1.38.17 | 0 / 8 | |
| 1.38.16 | 0 / 8 | |
| 1.38.15 | 0 / 8 | |
| 1.38.14 | 0 / 8 | |
| 1.38.13 | 0 / 8 | |
| 1.38.12 | 0 / 8 | |
| 1.38.11 | 0 / 8 | |
| 1.38.10 | 0 / 8 | |
| 1.38.9 | 0 / 8 | |
| 1.38.8 | 0 / 8 | |
| 1.38.7 | 0 / 8 | |
| 1.38.6 | 0 / 8 | |
| 1.38.5 | 0 / 8 | |
| 1.38.4 | 0 / 8 | |
| 1.38.3 | 0 / 8 | |
| 1.38.2 | 0 / 8 | |
| 1.38.1 | 0 / 8 | |
| 1.38.0 | 0 / 8 | |
| 1.37.1 | 0 / 8 | |
| 1.37.0 | 0 / 8 | |
| 1.36.2 | 0 / 8 | |
| 1.36.1 | 0 / 8 | |
| 1.36.0 | 0 / 8 | |
| 1.35.2 | 0 / 8 | |
| 1.35.1 | 0 / 8 | |
| 1.35.0 | 0 / 8 | |
| 1.34.2 | 0 / 8 | |
| 1.34.1 | 0 / 8 | |
| 1.34.0 | 0 / 8 | |
| 1.33.0 | 0 / 8 | |
| 1.32.2 | 0 / 8 | |
| 1.32.1 | 0 / 8 | |
| 1.32.0 | 0 / 8 | |
| 1.31.2 | 0 / 8 | |
| 1.31.1 | 0 / 8 | |
| 1.31.0 | 0 / 8 | |
| 1.30.4 | 0 / 8 | |
| 1.30.3 | 0 / 8 | |
| 1.30.2 | 0 / 8 | |
| 1.30.1 | 0 / 8 | |
| 1.30.0 | 0 / 8 | |
| 1.29.0 | 0 / 8 | |
| 1.28.2 | 0 / 8 |
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.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.38.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.38.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.38.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.38.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.38.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.38.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.38.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.38.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.38.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.38.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.38.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.38.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.38.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.38.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.38.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.38.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.38.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.38.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.38.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.38.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.38.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.38.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.38.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.38.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.38.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.38.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.38.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.38.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.38.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.38.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.38.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.38.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.38.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.38.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.38.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.38.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.38.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.38.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.38.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.38.3
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.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.36.1
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.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.35.1
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.0
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.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.1
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.
v1.30.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.29.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.28.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.