← Home

@radix-ui/react-visually-hidden

npm Repository Homepage

View docs [here](https://radix-ui.com/primitives/docs/utilities/visually-hidden).

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 missing-githead AI (provenance): Radix moved to GitHub Actions CI publishing; gitHead omission is expected with this workflow. ai
maintainer-change maintainer-removed AI (maintainer-change): Previous individual maintainers replaced by org account; known transition. ai
maintainer-change maintainer-added AI (maintainer-change): npm-workos is the WorkOS org account; legitimate Radix UI ownership transition. ai
bogus-package bogus-package AI (bogus-package): Radix UI component packages have minimal READMEs and no keywords by convention. ai
provenance publisher-changed AI (provenance): vladmoroz is a known Radix UI team member with extensive publish history; transition from benoitgrelard is a legitimate internal handoff within the same org. ai
provenance no-provenance AI (provenance): Radix UI packages historically published without Sigstore provenance; absence is not a risk signal for this established package. ai
npm-metadata no-description AI (npm-metadata): Established Radix UI package; missing description is a cosmetic issue, not a malware indicator for this well-known package. ai

Versions (showing 57 of 57)

Hide prereleases
Version Deps Published
1.2.7 1 / 7
1.2.6 1 / 7
1.2.5 1 / 7
1.2.4 1 / 9
1.2.3 1 / 9
1.2.2 1 / 9
1.2.1 1 / 9
1.2.0 1 / 9
1.1.3 1 / 0
1.1.2 1 / 0
1.1.1 1 / 0
1.1.0 1 / 0
1.0.3 2 / 0
1.0.2 2 / 0
1.0.1 2 / 0
1.0.0 2 / 0
0.1.4 2 / 0
0.1.3 2 / 0
0.1.2 2 / 0
0.1.1 2 / 0
0.1.0 2 / 0
0.0.15 3 / 0
0.0.14 3 / 0
0.0.13 3 / 0
0.0.12 3 / 0
0.0.11 3 / 0
0.0.10 3 / 0
0.0.9 3 / 0
0.0.8 3 / 0
0.0.7 3 / 0
0.0.6 2 / 0
0.0.5 3 / 0
0.0.4 3 / 0
0.0.3 3 / 0
0.0.2 3 / 0
0.0.1 2 / 1
1.2.4-rc.1761760880074 1 / 9
1.2.4-rc.1761757765388 1 / 9
1.2.4-rc.1761752560860 1 / 9
1.2.4-rc.1761750294484 1 / 9
1.2.4-rc.1761750045307 1 / 9
1.2.4-rc.1761621280215 1 / 9
1.2.4-rc.1761620575619 1 / 9
1.2.4-rc.1761619701743 1 / 9
1.2.4-rc.1761615925003 1 / 9
1.2.4-rc.1761614930803 1 / 9
1.2.4-rc.1761614469962 1 / 9
1.2.4-rc.1761582029795 1 / 9
1.2.3-rc.1747678980544 1 / 9
1.2.3-rc.1746560904918 1 / 9
1.2.1-rc.1746466567086 1 / 9
1.2.1-rc.1746075822931 1 / 9
1.2.1-rc.1746053194630 1 / 9
1.2.1-rc.1746044551800 1 / 9
1.2.1-rc.1745972185559 1 / 9
1.2.1-rc.1745439717073 1 / 9
1.2.1-rc.1745345395380 1 / 9

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

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

v1.2.5

3 findings
HIGH Missing gitHead — previous versions had it provenance

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 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 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.2.4

2 findings
HIGH Missing gitHead — previous versions had it provenance

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.

INFO No provenance attestation provenance

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

v1.2.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.2.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.2.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.2.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 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: chancestrickland.

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: benoitgrelard → 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.15

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.14

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.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. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.11

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 2021-03-26) provenance

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

v0.0.10

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 → jjenzz (on 2021-03-24) provenance

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

v0.0.9

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.8

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

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.6

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

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

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

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.