← Home

@radix-ui/react-toast

npm Repository Homepage

View docs [here](https://radix-ui.com/primitives/docs/components/toast).

5
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

hadihallakchancestricklandmark-workosnpm-workos

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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 5 of 5)

Version Deps Published
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

v1.2.16

2 findings
HIGH Publisher changed: chancestrickland → GitHub Actions (on 2026-06-06) provenance

This version was published by a different npm account than previous versions on 2026-06-06. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.2.15

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.2.14

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.2.13

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.2.12

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.