@box/tree
<!-- 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 342)
| Version | Deps | Published |
|---|---|---|
| 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.44 | 0 / 8 | |
| 1.37.43 | 0 / 8 | |
| 1.37.42 | 0 / 8 | |
| 1.37.41 | 0 / 8 | |
| 1.37.40 | 0 / 8 | |
| 1.37.39 | 0 / 8 | |
| 1.37.38 | 0 / 8 | |
| 1.37.37 | 0 / 8 | |
| 1.37.36 | 0 / 8 | |
| 1.37.35 | 0 / 8 | |
| 1.37.34 | 0 / 8 | |
| 1.37.33 | 0 / 8 | |
| 1.37.32 | 0 / 8 | |
| 1.37.31 | 0 / 8 | |
| 1.37.30 | 0 / 8 | |
| 1.37.29 | 0 / 8 | |
| 1.37.28 | 0 / 8 | |
| 1.37.27 | 0 / 8 | |
| 1.37.26 | 0 / 8 | |
| 1.37.25 | 0 / 8 | |
| 1.37.24 | 0 / 8 | |
| 1.37.23 | 0 / 8 | |
| 1.37.22 | 0 / 8 | |
| 1.37.21 | 0 / 8 | |
| 1.37.20 | 0 / 8 | |
| 1.37.19 | 0 / 8 | |
| 1.37.18 | 0 / 8 | |
| 1.37.17 | 0 / 8 | |
| 1.37.16 | 0 / 8 | |
| 1.37.15 | 0 / 8 | |
| 1.37.14 | 0 / 8 | |
| 1.37.13 | 0 / 8 | |
| 1.37.12 | 0 / 8 | |
| 1.37.11 | 0 / 8 | |
| 1.37.10 | 0 / 8 | |
| 1.37.9 | 0 / 8 | |
| 1.37.8 | 0 / 8 | |
| 1.37.7 | 0 / 8 | |
| 1.37.6 | 0 / 8 | |
| 1.37.5 | 0 / 8 | |
| 1.37.4 | 0 / 8 | |
| 1.37.3 | 0 / 8 | |
| 1.37.2 | 0 / 8 | |
| 1.37.1 | 0 / 8 | |
| 1.37.0 | 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.2 | 0 / 8 | |
| 1.33.1 | 0 / 8 | |
| 1.33.0 | 0 / 8 | |
| 1.32.0 | 0 / 8 | |
| 1.31.2 | 0 / 8 | |
| 1.31.1 | 0 / 8 | |
| 1.31.0 | 0 / 8 | |
| 1.30.2 | 0 / 8 | |
| 1.30.1 | 0 / 8 | |
| 1.30.0 | 0 / 8 | |
| 1.29.4 | 0 / 8 | |
| 1.29.3 | 0 / 8 | |
| 1.29.2 | 0 / 8 | |
| 1.29.1 | 0 / 8 | |
| 1.29.0 | 0 / 8 | |
| 1.28.0 | 0 / 8 | |
| 1.27.2 | 0 / 8 | |
| 1.27.1 | 0 / 8 | |
| 1.27.0 | 0 / 8 | |
| 1.26.5 | 0 / 8 | |
| 1.26.4 | 0 / 8 | |
| 1.26.3 | 0 / 8 | |
| 1.26.2 | 0 / 8 | |
| 1.26.1 | 0 / 8 | |
| 1.26.0 | 0 / 8 |
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.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.2
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.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.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.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.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.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.29.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.29.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.29.1
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.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.27.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.27.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.26.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.26.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.26.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.26.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.26.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.