@pierre/diffs
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 37 of 37)
| Version | Deps | Published |
|---|---|---|
| 1.2.7 | 6 / 15 | |
| 1.2.6 | 6 / 15 | |
| 1.2.5 | 6 / 15 | |
| 1.2.4 | 6 / 15 | |
| 1.2.3 | 6 / 15 | |
| 1.2.2 | 6 / 15 | |
| 1.2.1 | 6 / 15 | |
| 1.2.0 | 6 / 15 | |
| 1.1.22 | 6 / 13 | |
| 1.1.21 | 6 / 13 | |
| 1.1.20 | 6 / 13 | |
| 1.1.19 | 6 / 10 | |
| 1.1.18 | 6 / 10 | |
| 1.1.17 | 6 / 10 | |
| 1.1.16 | 6 / 10 | |
| 1.1.15 | 6 / 10 | |
| 1.1.14 | 6 / 10 | |
| 1.1.13 | 6 / 10 | |
| 1.1.12 | 6 / 10 | |
| 1.1.11 | 6 / 10 | |
| 1.1.10 | 6 / 10 | |
| 1.1.9 | 6 / 10 | |
| 1.1.8 | 6 / 10 | |
| 1.1.7 | 6 / 10 | |
| 1.1.6 | 6 / 10 | |
| 1.1.5 | 6 / 10 | |
| 1.1.4 | 6 / 10 | |
| 1.0.9 | 7 / 11 | |
| 1.0.8 | 7 / 11 | |
| 1.0.7 | 7 / 11 | |
| 1.0.6 | 7 / 11 | |
| 1.0.5 | 7 / 11 | |
| 1.0.4 | 7 / 11 | |
| 1.0.3 | 7 / 11 | |
| 1.0.2 | 7 / 11 | |
| 1.0.1 | 7 / 11 | |
| 1.0.0 | 7 / 11 |
v1.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.