@box/item-icon
<!-- 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 319)
| Version | Deps | Published |
|---|---|---|
| 2.32.14 | 0 / 7 | |
| 2.32.13 | 0 / 7 | |
| 2.32.12 | 0 / 7 | |
| 2.32.11 | 0 / 7 | |
| 2.32.10 | 0 / 7 | |
| 2.32.9 | 0 / 7 | |
| 2.32.8 | 0 / 7 | |
| 2.32.7 | 0 / 7 | |
| 2.32.6 | 0 / 7 | |
| 2.32.5 | 0 / 7 | |
| 2.32.4 | 0 / 7 | |
| 2.32.3 | 0 / 7 | |
| 2.32.2 | 0 / 7 | |
| 2.32.1 | 0 / 7 | |
| 2.32.0 | 0 / 7 | |
| 2.31.7 | 0 / 7 | |
| 2.31.6 | 0 / 7 | |
| 2.31.5 | 0 / 7 | |
| 2.31.4 | 0 / 7 | |
| 2.31.3 | 0 / 7 | |
| 2.31.2 | 0 / 7 | |
| 2.31.1 | 0 / 7 | |
| 2.31.0 | 0 / 7 | |
| 2.30.44 | 0 / 7 | |
| 2.30.43 | 0 / 7 | |
| 2.30.42 | 0 / 7 | |
| 2.30.41 | 0 / 7 | |
| 2.30.40 | 0 / 7 | |
| 2.30.39 | 0 / 7 | |
| 2.30.38 | 0 / 7 | |
| 2.30.37 | 0 / 7 | |
| 2.30.36 | 0 / 7 | |
| 2.30.35 | 0 / 7 | |
| 2.30.34 | 0 / 7 | |
| 2.30.33 | 0 / 7 | |
| 2.30.32 | 0 / 7 | |
| 2.30.31 | 0 / 7 | |
| 2.30.30 | 0 / 7 | |
| 2.30.29 | 0 / 7 | |
| 2.30.28 | 0 / 7 | |
| 2.30.27 | 0 / 7 | |
| 2.30.26 | 0 / 7 | |
| 2.30.25 | 0 / 7 | |
| 2.30.24 | 0 / 7 | |
| 2.30.23 | 0 / 7 | |
| 2.30.22 | 0 / 7 | |
| 2.30.21 | 0 / 7 | |
| 2.30.20 | 0 / 7 | |
| 2.30.19 | 0 / 7 | |
| 2.30.18 | 0 / 7 | |
| 2.30.17 | 0 / 7 | |
| 2.30.16 | 0 / 7 | |
| 2.30.15 | 0 / 7 | |
| 2.30.14 | 0 / 7 | |
| 2.30.13 | 0 / 7 | |
| 2.30.12 | 0 / 7 | |
| 2.30.11 | 0 / 7 | |
| 2.30.10 | 0 / 7 | |
| 2.30.9 | 0 / 7 | |
| 2.30.8 | 0 / 7 | |
| 2.30.7 | 0 / 7 | |
| 2.30.6 | 0 / 7 | |
| 2.30.5 | 0 / 7 | |
| 2.30.4 | 0 / 7 | |
| 2.30.3 | 0 / 7 | |
| 2.30.2 | 0 / 7 | |
| 2.30.1 | 0 / 7 | |
| 2.30.0 | 0 / 7 | |
| 2.29.1 | 0 / 7 | |
| 2.29.0 | 0 / 7 | |
| 2.28.2 | 0 / 7 | |
| 2.28.1 | 0 / 7 | |
| 2.28.0 | 0 / 7 | |
| 2.27.2 | 0 / 7 | |
| 2.27.1 | 0 / 7 | |
| 2.27.0 | 0 / 7 | |
| 2.26.2 | 0 / 7 | |
| 2.26.1 | 0 / 7 | |
| 2.26.0 | 0 / 7 | |
| 2.25.0 | 0 / 7 | |
| 2.24.2 | 0 / 7 | |
| 2.24.1 | 0 / 7 | |
| 2.24.0 | 0 / 7 | |
| 2.23.2 | 0 / 7 | |
| 2.23.1 | 0 / 7 | |
| 2.23.0 | 0 / 7 | |
| 2.22.4 | 0 / 7 | |
| 2.22.3 | 0 / 7 | |
| 2.22.2 | 0 / 7 | |
| 2.22.1 | 0 / 7 | |
| 2.22.0 | 0 / 7 | |
| 2.21.0 | 0 / 7 | |
| 2.20.2 | 0 / 7 | |
| 2.20.1 | 0 / 7 | |
| 2.20.0 | 0 / 7 | |
| 2.19.2 | 0 / 7 | |
| 2.19.1 | 0 / 7 | |
| 2.19.0 | 0 / 7 | |
| 2.18.2 | 0 / 7 | |
| 2.18.1 | 0 / 7 |
v2.31.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.31.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.31.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.30.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.30.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.30.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.30.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.30.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.30.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.30.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.30.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.30.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.30.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.30.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.30.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.30.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.30.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.30.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.30.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.30.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.30.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.30.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.30.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.30.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.30.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.30.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.30.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.30.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.30.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.30.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.30.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.30.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.30.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.30.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.30.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.30.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.30.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.30.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.30.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.30.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.30.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.30.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.30.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.30.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.30.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.30.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.30.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.30.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.29.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.29.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.28.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.28.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.28.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.27.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.27.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.26.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.26.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.24.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.24.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.23.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.23.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.22.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.22.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.22.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.22.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.20.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.20.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.19.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.19.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.18.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.18.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.