← Home

@radix-ui/react-primitive

npm Repository Homepage

This is an internal utility, not intended for public usage.

57
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): benoitgrelard is a known Radix UI core contributor; the transition from jjenzz is a legitimate internal team handoff within the radix-ui org, not a takeover. ai
maintainer-change maintainer-removed AI (maintainer-change): Removal of jjenzz reflects the same legitimate Radix UI team transition; benoitgrelard is a well-established publisher with 554 approved packages. ai
npm-metadata no-description AI (npm-metadata): Scoped monorepo packages in @radix-ui commonly omit descriptions; not a meaningful risk signal for this package. ai
bogus-package bogus-package AI (bogus-package): Radix UI packages intentionally have minimal READMEs and no keywords in their scoped packages. S_KNOWN_SPAM_PUBLISHER is a false positive for the legitimate Radix UI/WorkOS team. ai
provenance missing-githead AI (provenance): Radix UI monorepo tooling change explains missing gitHead; no security implication for this established package. ai
provenance no-provenance AI (provenance): Established Radix UI package; lack of Sigstore provenance is a process gap, not a security risk for this well-known library. ai

Versions (showing 57 of 57)

Hide prereleases
Version Deps Published
2.1.7 1 / 7
2.1.6 1 / 7
2.1.5 1 / 7
2.1.4 1 / 9
2.1.3 1 / 9
2.1.2 1 / 9
2.1.1 1 / 9
2.1.0 1 / 9
2.0.3 1 / 8
2.0.2 1 / 8
2.0.1 1 / 1
2.0.0 1 / 1
1.0.3 2 / 1
1.0.2 2 / 1
1.0.1 2 / 1
1.0.0 2 / 1
0.1.4 2 / 1
0.1.3 2 / 1
0.1.2 2 / 1
0.1.1 2 / 1
0.1.0 2 / 1
0.0.15 2 / 1
0.0.14 2 / 1
0.0.13 2 / 1
0.0.12 2 / 1
0.0.11 2 / 1
0.0.10 2 / 1
0.0.9 2 / 1
0.0.8 2 / 1
0.0.7 2 / 1
0.0.6 1 / 1
0.0.5 1 / 1
0.0.4 2 / 0
0.0.3 2 / 0
0.0.2 2 / 0
0.0.1 2 / 0
2.1.4-rc.1761760880074 1 / 9
2.1.4-rc.1761757765388 1 / 9
2.1.4-rc.1761752560860 1 / 9
2.1.4-rc.1761750294484 1 / 9
2.1.4-rc.1761750045307 1 / 9
2.1.4-rc.1761621280215 1 / 9
2.1.4-rc.1761620575619 1 / 9
2.1.4-rc.1761619701743 1 / 9
2.1.4-rc.1761615925003 1 / 9
2.1.4-rc.1761614930803 1 / 9
2.1.4-rc.1761614469962 1 / 9
2.1.4-rc.1761582029795 1 / 9
2.1.3-rc.1747678980544 1 / 9
2.1.3-rc.1746560904918 1 / 9
2.1.1-rc.1746466567086 1 / 9
2.1.1-rc.1746075822931 1 / 9
2.1.1-rc.1746053194630 1 / 9
2.1.1-rc.1746044551800 1 / 9
2.1.1-rc.1745972185559 1 / 9
2.1.1-rc.1745439717073 1 / 9
2.1.1-rc.1745345395380 1 / 9

v2.1.7

1 finding
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.

v2.1.6

2 findings
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.

INFO Missing gitHead — previous versions had it provenance

[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: GitHub Actions.

v2.1.5

3 findings
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.

INFO Missing gitHead — previous versions had it provenance

[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: GitHub Actions.

INFO Publisher changed: chancestrickland → GitHub Actions (on 2026-06-06) provenance

[Accepted risk] 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.

v1.0.3

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.2

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.0

2 findings
HIGH Publisher changed: jjenzz → benoitgrelard (on 2022-07-20) provenance

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

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.