@box/metadata-view
<!-- 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 375)
| Version | Deps | Published |
|---|---|---|
| 1.54.11 | 0 / 11 | |
| 1.54.10 | 0 / 11 | |
| 1.54.9 | 0 / 11 | |
| 1.54.8 | 0 / 11 | |
| 1.54.7 | 0 / 11 | |
| 1.54.6 | 0 / 11 | |
| 1.54.5 | 0 / 11 | |
| 1.54.4 | 0 / 11 | |
| 1.54.3 | 0 / 11 | |
| 1.54.2 | 0 / 11 | |
| 1.54.1 | 0 / 11 | |
| 1.54.0 | 0 / 11 | |
| 1.53.28 | 0 / 11 | |
| 1.53.27 | 0 / 11 | |
| 1.53.26 | 0 / 11 | |
| 1.53.25 | 0 / 11 | |
| 1.53.24 | 0 / 11 | |
| 1.53.23 | 0 / 10 | |
| 1.53.22 | 0 / 10 | |
| 1.53.21 | 0 / 10 | |
| 1.53.20 | 0 / 10 | |
| 1.53.19 | 0 / 10 | |
| 1.53.18 | 0 / 10 | |
| 1.53.17 | 0 / 10 | |
| 1.53.16 | 0 / 10 | |
| 1.53.15 | 0 / 10 | |
| 1.53.14 | 0 / 10 | |
| 1.53.13 | 0 / 10 | |
| 1.53.12 | 0 / 10 | |
| 1.53.11 | 0 / 10 | |
| 1.53.10 | 0 / 10 | |
| 1.53.9 | 0 / 10 | |
| 1.53.8 | 0 / 10 | |
| 1.53.7 | 0 / 10 | |
| 1.53.6 | 0 / 10 | |
| 1.53.5 | 0 / 10 | |
| 1.53.4 | 0 / 10 | |
| 1.53.3 | 0 / 10 | |
| 1.53.2 | 0 / 10 | |
| 1.53.1 | 0 / 10 | |
| 1.53.0 | 0 / 10 | |
| 1.52.5 | 0 / 10 | |
| 1.52.4 | 0 / 10 | |
| 1.52.3 | 0 / 10 | |
| 1.52.2 | 0 / 10 | |
| 1.52.1 | 0 / 10 | |
| 1.52.0 | 0 / 10 | |
| 1.51.25 | 0 / 10 | |
| 1.51.24 | 0 / 10 | |
| 1.51.23 | 0 / 10 | |
| 1.51.22 | 0 / 10 | |
| 1.51.21 | 0 / 10 | |
| 1.51.20 | 0 / 10 | |
| 1.51.19 | 0 / 10 | |
| 1.51.18 | 0 / 10 | |
| 1.51.17 | 0 / 10 | |
| 1.51.16 | 0 / 10 | |
| 1.51.15 | 0 / 10 | |
| 1.51.14 | 0 / 10 | |
| 1.51.13 | 0 / 10 | |
| 1.51.12 | 0 / 10 | |
| 1.51.11 | 0 / 10 | |
| 1.51.10 | 0 / 10 | |
| 1.51.9 | 0 / 10 | |
| 1.51.8 | 0 / 10 | |
| 1.51.7 | 0 / 10 | |
| 1.51.6 | 0 / 10 | |
| 1.51.5 | 0 / 10 | |
| 1.51.4 | 0 / 10 | |
| 1.51.3 | 0 / 10 | |
| 1.51.2 | 0 / 10 | |
| 1.51.1 | 0 / 10 | |
| 1.51.0 | 0 / 10 | |
| 1.50.16 | 0 / 10 | |
| 1.50.15 | 0 / 10 | |
| 1.50.14 | 0 / 10 | |
| 1.50.13 | 0 / 10 | |
| 1.50.12 | 0 / 10 | |
| 1.50.11 | 0 / 10 | |
| 1.50.10 | 0 / 10 | |
| 1.50.9 | 0 / 10 | |
| 1.50.8 | 0 / 10 | |
| 1.50.7 | 0 / 10 | |
| 1.50.6 | 0 / 10 | |
| 1.50.5 | 0 / 10 | |
| 1.50.4 | 0 / 10 | |
| 1.50.3 | 0 / 10 | |
| 1.50.2 | 0 / 10 | |
| 1.50.1 | 0 / 10 | |
| 1.50.0 | 0 / 10 | |
| 1.49.1 | 0 / 10 | |
| 1.49.0 | 0 / 10 | |
| 1.48.3 | 0 / 10 | |
| 1.48.2 | 0 / 10 | |
| 1.48.1 | 0 / 10 | |
| 1.48.0 | 0 / 10 | |
| 1.47.2 | 0 / 10 | |
| 1.47.1 | 0 / 10 | |
| 1.47.0 | 0 / 10 | |
| 1.46.2 | 0 / 10 |
v1.53.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.53.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.53.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.53.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.52.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.52.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.52.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.52.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.52.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.52.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.51.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.51.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.51.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.51.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.51.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.51.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.51.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.51.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.51.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.51.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.51.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.51.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.51.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.51.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.51.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.51.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.51.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.51.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.51.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.51.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.51.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.51.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.51.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.51.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.51.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.51.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.50.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.50.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.50.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.50.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.50.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.50.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.50.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.50.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.50.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.50.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.50.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.50.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.50.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.50.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.50.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.50.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.50.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.49.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.49.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.48.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.48.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.48.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.48.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.47.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.47.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.47.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.46.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.