@reach/descendants — Greenflagged

A descendant index solution for better accessibility support in compound components

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

ryanflorencemjacksonchancestricklandblainekasten

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
bogus-package	bogus-package	AI (bogus-package): chancestrickland is the legitimate Reach UI maintainer with 1782 approved packages; spam flag is a false positive.	ai	2026/04/24
provenance	missing-githead	AI (provenance): Build environment change is consistent with tsup migration; publisher is the long-standing maintainer of Reach UI.	ai	2026/04/24
provenance	publisher-changed	AI (provenance): The mjackson → chancestrickland transition is the documented, legitimate handoff of Reach UI to Chance Strickland (React Training). This is stable for all versions of this package.	ai	2026/04/24
phantom-deps	phantom-dep:tslib	AI (phantom-deps): tslib is a declared dependency used as a TypeScript runtime helper; it is a known implicit dependency pattern and not a security concern for this package.	ai	2026/04/24

Versions (showing 30 of 30)

Version	Deps	Published
0.18.0	1 / 6	2022-10-13
0.17.0	2 / 2	2022-04-20
0.16.1	2 / 2	2021-08-02
0.16.0	2 / 2	2021-08-02
0.15.3	2 / 2	2021-07-10
0.15.2	2 / 2	2021-06-28
0.15.0	2 / 2	2021-04-07
0.14.0	2 / 2	2021-03-28
0.13.2	2 / 2	2021-02-21
0.13.1	2 / 2	2021-02-21
0.13.0	2 / 0	2021-01-26
0.12.1	2 / 0	2020-11-27
0.12.0	2 / 0	2020-11-26
0.11.2	2 / 0	2020-09-01
0.11.1	2 / 0	2020-09-01
0.11.0	2 / 0	2020-08-21
0.10.5	2 / 0	2020-06-24
0.10.4	2 / 0	2020-06-15
0.10.3	2 / 0	2020-05-21
0.10.2	2 / 0	2020-05-11
0.10.1	2 / 0	2020-04-22
0.10.0	2 / 0	2020-04-05
0.9.1	2 / 0	2020-03-19
0.9.0	2 / 0	2020-03-14
0.8.6	2 / 0	2020-03-06
0.8.5	2 / 0	2020-02-21
0.8.4	2 / 0	2020-02-15
0.8.3	2 / 0	2020-02-15
0.8.2	2 / 0	2020-02-08
0.1.0	2 / 0	2020-02-05

v0.18.0

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.

v0.17.0

1 finding

LOW No provenance attestation provenance

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

v0.16.1

1 finding

LOW No provenance attestation provenance

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

v0.16.0

1 finding

LOW No provenance attestation provenance

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

v0.15.3

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: mjackson → chancestrickland (on 2021-07-10) provenance

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

v0.15.2

1 finding

LOW No provenance attestation provenance

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

v0.15.0

1 finding

LOW No provenance attestation provenance

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

v0.14.0

1 finding

LOW No provenance attestation provenance

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

v0.13.2

1 finding

LOW No provenance attestation provenance

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

v0.13.1

1 finding

LOW No provenance attestation provenance

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

v0.13.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: chancestrickland → mjackson (on 2021-01-26) provenance

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

v0.12.1

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: chancestrickland → mjackson (on 2020-11-27) provenance

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

v0.12.0

2 findings

HIGH Publisher changed: mjackson → chancestrickland (on 2020-11-26) provenance

This version was published by a different npm account than previous versions on 2020-11-26. 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.

v0.11.2

1 finding

LOW No provenance attestation provenance

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

v0.11.1

1 finding

LOW No provenance attestation provenance

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

v0.11.0

1 finding

LOW No provenance attestation provenance

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

v0.10.5

1 finding

LOW No provenance attestation provenance

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

v0.10.4

1 finding

LOW No provenance attestation provenance

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

v0.10.3

1 finding

LOW No provenance attestation provenance

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

v0.10.2

1 finding

LOW No provenance attestation provenance

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

v0.10.1

1 finding

LOW No provenance attestation provenance

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

v0.10.0

1 finding

LOW No provenance attestation provenance

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

v0.9.1

1 finding

LOW No provenance attestation provenance

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

v0.9.0

1 finding

LOW No provenance attestation provenance

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

v0.8.6

1 finding

LOW No provenance attestation provenance

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

v0.8.5

1 finding

LOW No provenance attestation provenance

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

v0.8.4

1 finding

LOW No provenance attestation provenance

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

v0.8.3

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: chancestrickland → mjackson (on 2020-02-15) provenance

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

v0.8.2

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: chancestrickland → mjackson (on 2020-02-08) provenance

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

v0.1.0

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.