@radix-ui/react-dialog
View docs [here](https://radix-ui.com/primitives/docs/components/dialog).
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
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 maintainer transition to WorkOS team (chancestrickland); stable for this org. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Known WorkOS team members added as part of org transition. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Previous maintainers removed as part of known org transition. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy reflects org restructuring; radix-ui is actively maintained. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Radix UI primitives are well-known; sparse README is a monorepo artifact. | ai |
v1.1.15
2 findingsThis version was published by a different npm account than previous versions on 2025-08-13. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.