← Home

@radix-ui/react-toolbar

npm Repository Homepage

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

62
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

benoitgrelardstephenhaneyandy-hookhadihallakchancestricklandmark-workos

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Radix UI primitives are a well-established, widely-downloaded package family. Lack of Sigstore provenance is a process gap, not a security risk for this trusted publisher. ai
provenance publisher-changed AI (provenance): vladmoroz is a known Radix UI core maintainer; transition from benoitgrelard is a legitimate team handoff within the same org. ai
npm-metadata no-description AI (npm-metadata): Radix UI monorepo sub-packages commonly omit descriptions; not indicative of malice for this established package. ai
bogus-package bogus-package AI (bogus-package): Radix UI sub-package with 6.8M weekly downloads and 1891 days of history. Spam signals are false positives: known maintainer, legitimate monorepo component, short README is standard for this package family. ai

Versions (showing 62 of 62)

Hide prereleases
Version Deps Published
1.1.11 7 / 9
1.1.10 7 / 9
1.1.9 7 / 9
1.1.0 7 / 0
1.0.4 8 / 0
1.0.3 8 / 0
1.0.2 8 / 0
1.0.1 8 / 0
1.0.0 8 / 0
0.1.5 7 / 0
0.1.4 7 / 0
0.1.3 7 / 0
0.1.2 7 / 0
0.1.1 6 / 0
0.1.0 6 / 0
0.0.14 8 / 0
0.0.13 8 / 0
0.0.12 8 / 0
0.0.11 8 / 0
0.0.10 8 / 0
0.0.9 9 / 0
0.0.8 9 / 0
0.0.7 9 / 0
0.0.6 9 / 0
0.0.4 8 / 0
0.0.3 8 / 0
0.0.2 8 / 0
0.0.1 6 / 0
1.1.12-rc.1766004502650 7 / 9
1.1.12-rc.1762291353631 7 / 9
1.1.12-rc.1762290574118 7 / 9
1.1.11-rc.1761760880074 7 / 9
1.1.11-rc.1761757765388 7 / 9
1.1.11-rc.1761752560860 7 / 9
1.1.11-rc.1761750294484 7 / 9
1.1.11-rc.1761750045307 7 / 9
1.1.11-rc.1761621280215 7 / 9
1.1.11-rc.1761620575619 7 / 9
1.1.11-rc.1761619701743 7 / 9
1.1.11-rc.1761615925003 7 / 9
1.1.11-rc.1761614930803 7 / 9
1.1.11-rc.1761614469962 7 / 9
1.1.11-rc.1761582029795 7 / 9
1.1.11-rc.1761327012562 7 / 9
1.1.11-rc.1755205432459 7 / 9
1.1.11-rc.1755201399387 7 / 9
1.1.11-rc.1755118410828 7 / 9
1.1.11-rc.1755114563302 7 / 9
1.1.11-rc.1752791004720 7 / 9
1.1.11-rc.1752166910601 7 / 9
1.1.11-rc.1752166434368 7 / 9
1.1.11-rc.1752166197873 7 / 9
1.1.11-rc.1752165236204 7 / 9
1.1.10-rc.1747678980544 7 / 9
1.1.10-rc.1746560904918 7 / 9
1.1.8-rc.1746466567086 7 / 9
1.1.8-rc.1746075822931 7 / 9
1.1.8-rc.1746053194630 7 / 9
1.1.8-rc.1746044551800 7 / 9
1.1.8-rc.1745972185559 7 / 9
1.1.8-rc.1745439717073 7 / 9
1.1.8-rc.1745345395380 7 / 9

v1.1.11

1 finding
LOW No provenance attestation provenance

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

v1.1.10

1 finding
LOW No provenance attestation provenance

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

v1.1.9

1 finding
LOW No provenance attestation provenance

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

v1.1.0

2 findings
HIGH Publisher changed: benoitgrelard → vladmoroz (on 2024-06-19) provenance

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

LOW No provenance attestation provenance

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

v1.0.4

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.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
INFO No provenance attestation provenance

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

INFO Publisher changed: jjenzz → benoitgrelard (on 2022-07-20) provenance

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

v0.1.5

1 finding
INFO No provenance attestation provenance

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

v0.1.4

1 finding
INFO No provenance attestation provenance

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

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

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

v0.1.1

2 findings
INFO No provenance attestation provenance

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

INFO Publisher changed: andy-hook → jjenzz (on 2021-10-14) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2021-10-14. This could indicate a legitimate maintainer transition or an account compromise.

v0.1.0

2 findings
INFO No provenance attestation provenance

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

INFO Publisher changed: andy-hook → benoitgrelard (on 2021-09-07) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2021-09-07. This could indicate a legitimate maintainer transition or an account compromise.

v0.0.14

2 findings
INFO No provenance attestation provenance

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

INFO Publisher changed: benoitgrelard → andy-hook (on 2021-08-04) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2021-08-04. This could indicate a legitimate maintainer transition or an account compromise.

v0.0.13

1 finding
INFO No provenance attestation provenance

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

v0.0.12

1 finding
INFO No provenance attestation provenance

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

v0.0.11

1 finding
INFO No provenance attestation provenance

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

v0.0.10

1 finding
INFO No provenance attestation provenance

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

v0.0.9

1 finding
INFO No provenance attestation provenance

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

v0.0.8

1 finding
INFO No provenance attestation provenance

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

v0.0.7

1 finding
INFO No provenance attestation provenance

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

v0.0.6

1 finding
INFO No provenance attestation provenance

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

v0.0.4

1 finding
INFO No provenance attestation provenance

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

v0.0.3

1 finding
INFO No provenance attestation provenance

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

v0.0.2

1 finding
INFO No provenance attestation provenance

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

v0.0.1

1 finding
INFO No provenance attestation provenance

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