@radix-ui/react-toast
View docs [here](https://radix-ui.com/primitives/docs/components/toast).
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): Trusted Radix publisher; build-tooling change, no behavioral risk. | ai | |
| provenance | publisher-changed | AI (provenance): Legitimate transition to GitHub Actions CI/CD publishing with SLSA provenance for radix-ui org. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): npm-workos reflects WorkOS acquisition of Radix UI; known organizational change. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Old individual maintainers replaced by org account after WorkOS acquisition. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Monorepo sub-package; description omission is common and stable for radix-ui. | ai | |
| bogus-package | bogus-package | AI (bogus-package): False positive on a 24.6M downloads/week package; monorepo sub-package metadata pattern. | ai |
Versions (showing 31 of 31)
| Version | Deps | Published |
|---|---|---|
| 1.2.23 | 12 / 8 | |
| 1.2.22 | 12 / 8 | |
| 1.2.21 | 12 / 8 | |
| 1.2.20 | 12 / 8 | |
| 1.2.19 | 12 / 8 | |
| 1.2.18 | 12 / 8 | |
| 1.2.17 | 12 / 7 | |
| 1.2.16 | 12 / 7 | |
| 1.2.15 | 12 / 9 | |
| 1.2.14 | 12 / 9 | |
| 1.2.13 | 12 / 9 | |
| 1.2.12 | 12 / 9 | |
| 1.2.11 | 12 / 9 | |
| 1.2.10 | 12 / 9 | |
| 1.2.9 | 12 / 9 | |
| 1.2.8 | 12 / 9 | |
| 1.2.7 | 12 / 8 | |
| 1.2.6 | 12 / 8 | |
| 1.2.5 | 12 / 6 | |
| 1.2.4 | 12 / 0 | |
| 1.2.3 | 12 / 0 | |
| 1.2.2 | 12 / 0 | |
| 1.2.1 | 12 / 0 | |
| 1.2.0 | 12 / 0 | |
| 1.1.5 | 13 / 0 | |
| 1.1.4 | 13 / 0 | |
| 1.1.3 | 13 / 0 | |
| 1.1.2 | 13 / 0 | |
| 1.1.1 | 13 / 0 | |
| 1.1.0 | 13 / 0 | |
| 1.0.0 | 13 / 0 |
v1.2.23
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.22
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.21
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.20
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.19
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.18
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.11
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: chancestrickland.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.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: chancestrickland.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.9
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: chancestrickland.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.8
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: chancestrickland.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2024-10-01. This could indicate a legitimate maintainer transition or an account compromise.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
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 (benoitgrelard) than the most recent previously approved version (andy-hook) on 2023-05-26, but benoitgrelard 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.
v1.1.3
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 (benoitgrelard) than the most recent previously approved version (andy-hook) on 2023-03-08, but benoitgrelard 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.
v1.1.2
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 (andy-hook) than the most recent previously approved version (benoitgrelard) on 2022-11-15, but andy-hook 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.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.