@pubinfo-nightly/shared
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 13 of 113)
| Version | Deps | Published |
|---|---|---|
| 2025.11.27 | 1 / 1 | |
| 2025.11.26 | 1 / 1 | |
| 2025.11.25 | 1 / 1 | |
| 2025.11.24 | 1 / 1 | |
| 2025.11.23 | 1 / 1 | |
| 2025.11.22 | 1 / 1 | |
| 2025.11.21 | 1 / 1 | |
| 2025.11.20 | 1 / 1 | |
| 2025.11.19 | 1 / 1 | |
| 2025.11.18 | 1 / 1 | |
| 2025.11.17 | 1 / 1 | |
| 2025.11.16 | 1 / 1 | |
| 2025.11.15 | 1 / 1 |
v2025.11.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2025.11.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2025.11.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2025.11.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2025.11.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2025.11.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2025.11.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2025.11.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2025.11.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2025.11.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2025.11.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2025.11.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2025.11.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.