@radix-ui/react-roving-focus
This is an internal utility, not intended for public usage.
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| 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 47 of 47)
| 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 |
v1.1.19
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.18
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.17
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.16
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.15
4 findingsThis 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.
[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.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[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 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.12
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
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 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.7
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[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 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[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 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[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 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[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.