@next/react-refresh-utils
An experimental package providing utilities for React Refresh.
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 | missing-githead | AI (provenance): Next.js monorepo CI publishes without gitHead; stable pattern for this scoped package. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Vercel org restructuring; package still published via attested GitHub Actions CI/CD. | ai | |
| provenance | publisher-changed | AI (provenance): Transition from vercel-release-bot to GitHub Actions is an internal CI account change within the Vercel org, confirmed by SLSA attestation. | ai |
Versions (showing 70 of 70)
| Version | Deps | Published |
|---|---|---|
| 16.2.12 | 0 / 2 | |
| 16.2.11 | 0 / 2 | |
| 16.2.10 | 0 / 2 | |
| 16.2.9 | 0 / 2 | |
| 16.2.8 | 0 / 2 | |
| 16.2.7 | 0 / 2 | |
| 16.2.6 | 0 / 2 | |
| 16.2.5 | 0 / 2 | |
| 16.2.4 | 0 / 2 | |
| 16.2.3 | 0 / 2 | |
| 16.2.2 | 0 / 2 | |
| 16.2.1 | 0 / 2 | |
| 16.2.0 | 0 / 2 | |
| 16.1.7 | 0 / 2 | |
| 16.1.6 | 0 / 2 | |
| 16.1.5 | 0 / 2 | |
| 16.1.4 | 0 / 2 | |
| 16.1.3 | 0 / 2 | |
| 16.1.2 | 0 / 2 | |
| 16.1.1 | 0 / 2 | |
| 16.1.0 | 0 / 2 | |
| 16.0.11 | 0 / 2 | |
| 16.0.10 | 0 / 2 | |
| 16.0.9 | 0 / 2 | |
| 16.0.8 | 0 / 2 | |
| 16.0.7 | 0 / 2 | |
| 16.0.6 | 0 / 2 | |
| 16.0.5 | 0 / 2 | |
| 16.0.4 | 0 / 2 | |
| 16.0.3 | 0 / 2 | |
| 16.0.2 | 0 / 2 | |
| 16.0.1 | 0 / 2 | |
| 16.0.0 | 0 / 2 | |
| 15.5.22 | 0 / 2 | |
| 15.5.21 | 0 / 2 | |
| 15.5.20 | 0 / 2 | |
| 15.5.19 | 0 / 2 | |
| 15.5.18 | 0 / 2 | |
| 15.5.16 | 0 / 2 | |
| 15.5.15 | 0 / 2 | |
| 15.5.14 | 0 / 2 | |
| 15.5.13 | 0 / 2 | |
| 15.5.12 | 0 / 2 | |
| 15.5.11 | 0 / 2 | |
| 15.5.10 | 0 / 2 | |
| 15.5.9 | 0 / 2 | |
| 15.5.8 | 0 / 2 | |
| 15.5.7 | 0 / 2 | |
| 15.4.11 | 0 / 2 | |
| 15.4.10 | 0 / 2 | |
| 15.4.9 | 0 / 2 | |
| 15.4.8 | 0 / 2 | |
| 15.3.9 | 0 / 2 | |
| 15.3.8 | 0 / 2 | |
| 15.3.7 | 0 / 2 | |
| 15.3.6 | 0 / 2 | |
| 15.2.9 | 0 / 2 | |
| 15.2.8 | 0 / 2 | |
| 15.2.7 | 0 / 2 | |
| 15.2.6 | 0 / 2 | |
| 15.1.12 | 0 / 2 | |
| 15.1.11 | 0 / 2 | |
| 15.1.10 | 0 / 2 | |
| 15.1.9 | 0 / 2 | |
| 15.0.8 | 0 / 2 | |
| 15.0.7 | 0 / 2 | |
| 15.0.6 | 0 / 2 | |
| 15.0.5 | 0 / 2 | |
| 14.2.35 | 0 / 2 | |
| 14.2.34 | 0 / 2 |
v16.2.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v16.2.11
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
v16.2.10
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v15.5.22
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
v15.5.21
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
v15.5.20
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.