@prismicio/react
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 3.4.1 | 1 / 12 | |
| 3.4.0 | 1 / 14 | |
| 3.3.0 | 1 / 14 | |
| 3.2.2 | 1 / 27 | |
| 3.2.1 | 1 / 27 | |
| 3.2.0 | 1 / 27 | |
| 3.1.0 | 1 / 27 | |
| 3.0.0 | 1 / 27 |
v3.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 (angeloashmore) than the most recent previously approved version (levimykel) on 2025-04-14, but angeloashmore 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.
v3.2.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 (xrutayisire) than the most recent previously approved version (levimykel) on 2025-03-19, but xrutayisire 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.
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.