@box/metadata-editor
<!-- 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 367)
| Version | Deps | Published |
|---|---|---|
| 1.62.3 | 0 / 10 | |
| 1.62.2 | 0 / 10 | |
| 1.62.1 | 0 / 10 | |
| 1.62.0 | 0 / 10 | |
| 1.61.5 | 0 / 10 | |
| 1.61.4 | 0 / 10 | |
| 1.61.3 | 0 / 10 | |
| 1.61.2 | 0 / 10 | |
| 1.61.1 | 0 / 10 | |
| 1.61.0 | 0 / 10 | |
| 1.60.0 | 0 / 10 | |
| 1.59.7 | 0 / 10 | |
| 1.59.6 | 0 / 10 | |
| 1.59.5 | 0 / 10 | |
| 1.59.4 | 0 / 10 | |
| 1.59.3 | 0 / 10 | |
| 1.59.2 | 0 / 10 | |
| 1.59.1 | 0 / 10 | |
| 1.59.0 | 0 / 10 | |
| 1.58.4 | 0 / 10 | |
| 1.58.3 | 0 / 10 | |
| 1.58.2 | 0 / 10 | |
| 1.58.1 | 0 / 10 | |
| 1.58.0 | 0 / 10 | |
| 1.57.5 | 0 / 10 | |
| 1.57.4 | 0 / 10 | |
| 1.57.3 | 0 / 10 | |
| 1.57.2 | 0 / 10 | |
| 1.57.1 | 0 / 10 | |
| 1.57.0 | 0 / 10 | |
| 1.56.2 | 0 / 10 | |
| 1.56.1 | 0 / 10 | |
| 1.56.0 | 0 / 10 | |
| 1.55.6 | 0 / 10 | |
| 1.55.5 | 0 / 10 | |
| 1.55.4 | 0 / 10 | |
| 1.55.3 | 0 / 10 | |
| 1.55.2 | 0 / 10 | |
| 1.55.1 | 0 / 10 | |
| 1.55.0 | 0 / 10 | |
| 1.54.3 | 0 / 10 | |
| 1.54.2 | 0 / 10 | |
| 1.54.1 | 0 / 10 | |
| 1.54.0 | 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.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.0 | 0 / 10 | |
| 1.49.0 | 0 / 10 | |
| 1.48.1 | 0 / 10 | |
| 1.48.0 | 0 / 10 | |
| 1.47.1 | 0 / 10 | |
| 1.47.0 | 0 / 10 | |
| 1.46.2 | 0 / 10 | |
| 1.46.1 | 0 / 10 | |
| 1.46.0 | 0 / 10 | |
| 1.45.0 | 0 / 10 | |
| 1.44.2 | 0 / 10 | |
| 1.44.1 | 0 / 10 | |
| 1.44.0 | 0 / 10 | |
| 1.43.2 | 0 / 10 | |
| 1.43.1 | 0 / 10 | |
| 1.43.0 | 0 / 10 | |
| 1.42.0 | 0 / 10 | |
| 1.41.0 | 0 / 10 | |
| 1.40.2 | 0 / 10 | |
| 1.40.1 | 0 / 10 | |
| 1.40.0 | 0 / 10 | |
| 1.39.2 | 0 / 10 | |
| 1.39.1 | 0 / 10 | |
| 1.39.0 | 0 / 10 |
v1.57.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.57.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.57.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.56.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.56.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.56.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.55.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.55.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.55.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.55.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.55.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.55.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.55.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.54.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.54.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.54.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.54.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.53.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.53.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.53.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.53.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.53.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.53.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.53.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.53.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.53.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.53.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.53.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.53.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.53.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.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.0
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.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.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.
v1.46.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.46.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.45.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.44.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.44.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.44.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.43.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.43.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.43.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.42.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.41.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.40.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.40.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.40.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.