@radix-ui/react-portal
View docs [here](https://radix-ui.com/primitives/docs/utilities/portal).
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): Legitimate migration to GitHub Actions CI/CD publishing for the radix-ui org. | ai | |
| provenance | missing-githead | AI (provenance): Expected when switching to GitHub Actions publishing with SLSA provenance. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): npm-workos reflects WorkOS acquisition of Radix UI; legitimate org change. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Old individual maintainers replaced by org account after WorkOS acquisition. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Radix UI component package; low README detail is normal for monorepo sub-packages. | ai | |
| provenance | no-provenance | AI (provenance): Radix UI publishes without provenance; stable pattern for this org. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 1.1.13 | 2 / 7 | |
| 1.1.12 | 2 / 7 | |
| 1.1.11 | 2 / 7 | |
| 1.1.10 | 2 / 9 | |
| 1.1.9 | 2 / 9 | |
| 1.1.8 | 2 / 9 | |
| 1.1.7 | 2 / 9 | |
| 1.1.6 | 2 / 9 | |
| 1.1.5 | 2 / 8 | |
| 1.1.4 | 2 / 8 | |
| 1.1.3 | 2 / 0 | |
| 1.1.2 | 2 / 0 | |
| 1.1.1 | 2 / 0 | |
| 1.1.0 | 1 / 0 |
v1.1.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.11
3 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.
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.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.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.1.7
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.1.6
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[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: chancestrickland.
v1.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
2 findings[Accepted risk] Package 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.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.