← Home

@radix-ui/react-focus-scope

npm Repository Homepage

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

7
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): Legitimate migration to GitHub Actions CI/CD publishing for the radix-ui org. ai
provenance missing-githead AI (provenance): Expected when switching to GitHub Actions publishing with SLSA provenance. ai
maintainer-change maintainer-added AI (maintainer-change): npm-workos reflects WorkOS acquisition of Radix UI; legitimate org change. ai
maintainer-change maintainer-removed AI (maintainer-change): Previous individual maintainers replaced by org account after WorkOS acquisition. ai
npm-metadata no-description AI (npm-metadata): Radix UI packages historically omit descriptions; not a spam signal here. ai
bogus-package bogus-package AI (bogus-package): Radix UI monorepo sub-package; minimal README and no keywords are normal for scoped primitives. ai

Versions (showing 7 of 7)

Version Deps Published
1.1.10 3 / 7
1.1.9 3 / 7
1.1.8 3 / 9
1.1.7 3 / 9
1.1.6 3 / 9
1.1.5 3 / 9
1.1.2 3 / 8

v1.1.10

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

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.

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

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.

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

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.

LOW No provenance attestation provenance

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

v1.1.5

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.

LOW No provenance attestation provenance

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

v1.1.2

1 finding
LOW No provenance attestation provenance

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