@canonical/react-head
Declarative head management for React with SSR collection
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from manual publish to GitHub Actions CI/CD with SLSA attestation; expected for canonical org packages. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): mariadias143 removed as part of automated CI/CD publish transition; consistent with org-level pipeline adoption. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 0.33.0 | 1 / 18 | |
| 0.32.0 | 1 / 18 | |
| 0.31.0 | 1 / 18 | |
| 0.30.0 | 1 / 18 | |
| 0.29.0 | 1 / 17 | |
| 0.28.0 | 1 / 17 | |
| 0.27.0 | 1 / 17 | |
| 0.26.0 | 1 / 17 | |
| 0.25.0 | 1 / 17 |
v0.33.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.32.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.31.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.30.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.29.0
2 findingsThis version was published by a different npm account than previous versions on 2026-07-03. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.26.0
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 (mariadias143) than the most recent previously approved version (ad.vl) on 2026-04-24, but mariadias143 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.