@radix-ui/primitive
This is an internal utility, not intended for public usage.
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 from Radix UI to WorkOS team (chancestrickland). | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): WorkOS acquisition of Radix UI; new maintainers are known team members. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Old Radix maintainers replaced by WorkOS team as part of known transition. | ai |
Versions (showing 31 of 31)
| Version | Deps | Published |
|---|---|---|
| 1.1.3 | 0 / 5 | |
| 1.1.2 | 0 / 4 | |
| 1.1.1 | 0 / 0 | |
| 1.0.1 | 1 / 0 | |
| 1.0.0 | 1 / 0 | |
| 0.0.5 | 1 / 0 | |
| 0.0.3 | 1 / 0 | |
| 0.0.2 | 1 / 0 | |
| 0.0.1 | 0 / 0 | |
| 1.1.3-rc.1761760880074 | 0 / 5 | |
| 1.1.3-rc.1761757765388 | 0 / 5 | |
| 1.1.3-rc.1761752560860 | 0 / 5 | |
| 1.1.3-rc.1761750294484 | 0 / 5 | |
| 1.1.3-rc.1761750045307 | 0 / 5 | |
| 1.1.3-rc.1761621280215 | 0 / 5 | |
| 1.1.3-rc.1761620575619 | 0 / 5 | |
| 1.1.3-rc.1761619701743 | 0 / 5 | |
| 1.1.3-rc.1761615925003 | 0 / 5 | |
| 1.1.3-rc.1761614930803 | 0 / 5 | |
| 1.1.3-rc.1761614469962 | 0 / 5 | |
| 1.1.3-rc.1761582029795 | 0 / 5 | |
| 1.1.3-rc.1761327012562 | 0 / 5 | |
| 1.1.3-rc.1755205432459 | 0 / 5 | |
| 1.1.3-rc.1755201399387 | 0 / 5 | |
| 1.1.3-rc.1755118410828 | 0 / 5 | |
| 1.1.3-rc.1755114563302 | 0 / 5 | |
| 1.1.3-rc.1752791004720 | 0 / 5 | |
| 1.1.3-rc.1752166910601 | 0 / 5 | |
| 1.1.3-rc.1752166434368 | 0 / 5 | |
| 1.1.3-rc.1752166197873 | 0 / 5 | |
| 1.1.3-rc.1752165236204 | 0 / 5 |
v1.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
2 findingsThis version was published by a different npm account than previous versions on 2024-12-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.1
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.