← Home

@radix-ui/react-roving-focus

npm Repository Homepage

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

81
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): Publish env moved to SLSA-attested CI/CD; gitHead absence expected, provenance improved. ai
maintainer-change maintainer-added AI (maintainer-change): Known radix-ui→WorkOS org transition; benign for this package. ai
provenance publisher-changed AI (provenance): benoitgrelard is a known Radix UI core contributor; publisher transition is a legitimate internal team change within the radix-ui org, not a hostile takeover. ai
maintainer-change maintainer-removed AI (maintainer-change): Maintainer changes reflect internal Radix UI team restructuring; package remains under the official radix-ui GitHub org with consistent metadata. ai
publish-pattern new-deps-added AI (publish-pattern): @radix-ui/react-direction is a first-party Radix UI package; adding it is a legitimate feature addition (LTR/RTL support) not a supply chain risk. ai
bogus-package bogus-package AI (bogus-package): 60.9M dl/wk official radix-ui monorepo package; README/keyword heuristics are stable FPs. ai

Versions (showing 81 of 81)

Hide prereleases
Version Deps Published
1.1.19 11 / 7
1.1.18 11 / 7
1.1.17 11 / 7
1.1.16 11 / 7
1.1.15 11 / 7
1.1.14 9 / 7
1.1.13 9 / 7
1.1.12 9 / 7
1.1.11 9 / 9
1.1.10 9 / 9
1.1.9 9 / 9
1.1.8 9 / 9
1.1.7 9 / 9
1.1.6 9 / 9
1.1.5 9 / 9
1.1.4 9 / 9
1.1.3 9 / 8
1.1.2 9 / 8
1.1.1 9 / 0
1.1.0 9 / 0
1.0.4 10 / 0
1.0.3 10 / 0
1.0.2 10 / 0
1.0.1 10 / 0
1.0.0 10 / 0
0.1.5 9 / 0
0.1.4 9 / 0
0.1.3 9 / 0
0.1.2 9 / 0
0.1.1 9 / 0
0.1.0 9 / 0
0.0.16 10 / 0
0.0.15 10 / 0
0.0.14 10 / 0
0.0.13 10 / 0
0.0.12 10 / 0
0.0.11 5 / 0
0.0.10 5 / 0
0.0.9 5 / 0
0.0.8 5 / 0
0.0.7 5 / 0
0.0.6 4 / 0
0.0.5 2 / 0
0.0.4 2 / 0
0.0.3 2 / 0
0.0.2 2 / 0
0.0.1 2 / 1
1.1.12-rc.1766004502650 9 / 9
1.1.12-rc.1762291353631 9 / 9
1.1.12-rc.1762290574118 9 / 9
1.1.11-rc.1761760880074 9 / 9
1.1.11-rc.1761757765388 9 / 9
1.1.11-rc.1761752560860 9 / 9
1.1.11-rc.1761750294484 9 / 9
1.1.11-rc.1761750045307 9 / 9
1.1.11-rc.1761621280215 9 / 9
1.1.11-rc.1761620575619 9 / 9
1.1.11-rc.1761619701743 9 / 9
1.1.11-rc.1761615925003 9 / 9
1.1.11-rc.1761614930803 9 / 9
1.1.11-rc.1761614469962 9 / 9
1.1.11-rc.1761582029795 9 / 9
1.1.11-rc.1761327012562 9 / 9
1.1.11-rc.1755205432459 9 / 9
1.1.11-rc.1755201399387 9 / 9
1.1.11-rc.1755118410828 9 / 9
1.1.11-rc.1755114563302 9 / 9
1.1.11-rc.1752791004720 9 / 9
1.1.11-rc.1752166910601 9 / 9
1.1.11-rc.1752166434368 9 / 9
1.1.11-rc.1752166197873 9 / 9
1.1.11-rc.1752165236204 9 / 9
1.1.10-rc.1747678980544 9 / 9
1.1.10-rc.1746560904918 9 / 9
1.1.8-rc.1746466567086 9 / 9
1.1.8-rc.1746075822931 9 / 9
1.1.8-rc.1746053194630 9 / 9
1.1.8-rc.1746044551800 9 / 9
1.1.8-rc.1745972185559 9 / 9
1.1.8-rc.1745439717073 9 / 9
1.1.8-rc.1745345395380 9 / 9

v1.1.19

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

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

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

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

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

HIGH Low-value / spam package indicators (3 signals, score 4) bogus-package

[Reject — re-review on republish] (prior reject: AI (bogus-package): Inflated first semver (1.1.11) on a single-version package published under the @radix-ui namespace by a non-official publisher is a persistent impersonation signal across all versi) Matched 3 signal(s), weighted score 4: • [S_README_NO_CODE] Short README with no code block, no install instructions, and no usage/API section. • [S_DESC_MATCHES_NAME] Description is empty or just restates the package name. • [S_NO_KEYWORDS] No keywords declared.

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-07-06) provenance

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

v1.1.14

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

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

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 Publisher changed: chancestrickland → GitHub Actions (on 2026-06-06, now via trusted publisher with provenance) provenance

This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (chancestrickland) on 2026-06-06, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.

v1.1.11

2 findings
LOW No provenance attestation provenance

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.

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

1 finding
LOW No provenance attestation provenance

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

v1.1.7

2 findings
LOW No provenance attestation provenance

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.

v1.1.6

2 findings
LOW No provenance attestation provenance

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.

v1.1.5

2 findings
LOW No provenance attestation provenance

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.

v1.1.4

2 findings
LOW No provenance attestation provenance

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.

v1.1.12-rc.1766004502650

1 finding
LOW No provenance attestation provenance

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

v1.1.12-rc.1762291353631

1 finding
LOW No provenance attestation provenance

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

v1.1.12-rc.1762290574118

2 findings
LOW No provenance attestation provenance

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.

v1.1.11-rc.1761760880074

2 findings
LOW No provenance attestation provenance

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.

v1.1.11-rc.1761757765388

1 finding
LOW No provenance attestation provenance

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

v1.1.11-rc.1761752560860

1 finding
LOW No provenance attestation provenance

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

v1.1.11-rc.1761750294484

1 finding
LOW No provenance attestation provenance

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

v1.1.11-rc.1761750045307

1 finding
LOW No provenance attestation provenance

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

v1.1.11-rc.1761621280215

1 finding
LOW No provenance attestation provenance

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

v1.1.11-rc.1761620575619

1 finding
LOW No provenance attestation provenance

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

v1.1.11-rc.1761619701743

1 finding
LOW No provenance attestation provenance

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

v1.1.11-rc.1761615925003

1 finding
LOW No provenance attestation provenance

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

v1.1.11-rc.1761614930803

1 finding
LOW No provenance attestation provenance

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

v1.1.11-rc.1761614469962

1 finding
LOW No provenance attestation provenance

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

v1.1.11-rc.1761582029795

1 finding
LOW No provenance attestation provenance

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

v1.1.11-rc.1761327012562

1 finding
LOW No provenance attestation provenance

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

v1.1.11-rc.1755205432459

1 finding
LOW No provenance attestation provenance

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

v1.1.11-rc.1755201399387

1 finding
LOW No provenance attestation provenance

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

v1.1.11-rc.1755118410828

1 finding
LOW No provenance attestation provenance

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

v1.1.11-rc.1755114563302

1 finding
LOW No provenance attestation provenance

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

v1.1.11-rc.1752791004720

1 finding
LOW No provenance attestation provenance

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

v1.1.11-rc.1752166910601

1 finding
LOW No provenance attestation provenance

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

v1.1.11-rc.1752166434368

1 finding
LOW No provenance attestation provenance

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

v1.1.11-rc.1752166197873

1 finding
LOW No provenance attestation provenance

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

v1.1.11-rc.1752165236204

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

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

1 finding
LOW No provenance attestation provenance

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

v1.1.8-rc.1746466567086

1 finding
LOW No provenance attestation provenance

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

v1.1.8-rc.1746075822931

1 finding
LOW No provenance attestation provenance

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

v1.1.8-rc.1746053194630

1 finding
LOW No provenance attestation provenance

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

v1.1.8-rc.1746044551800

1 finding
LOW No provenance attestation provenance

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

v1.1.8-rc.1745972185559

2 findings
LOW No provenance attestation provenance

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.

v1.1.8-rc.1745439717073

1 finding
LOW No provenance attestation provenance

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

v1.1.8-rc.1745345395380

2 findings
LOW No provenance attestation provenance

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.