@abgov/react-components
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
Keywords
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 7.2.1 | 0 / 0 | |
| 7.1.0 | 0 / 0 | |
| 7.0.0 | 0 / 0 | |
| 6.9.3 | 0 / 0 | |
| 6.9.2 | 0 / 0 | |
| 6.9.1 | 0 / 0 | |
| 6.9.0 | 0 / 0 |
v7.2.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (dustin.nielsen) than the most recent previously approved version (abgov-chris-olsen) on 2026-06-01, but dustin.nielsen is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v7.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.