@reach/combobox — Greenflagged

Accessible React Combobox (Autocomplete).

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
provenance	publisher-changed	AI (provenance): chancestrickland is the documented primary maintainer of reach-ui; the transition from mjackson is a known legitimate handoff within the React Training / Reach UI project.	ai	2026/04/24
provenance	missing-githead	AI (provenance): Absence of gitHead reflects a build environment change (tsdx build), not a security concern. Package content and source maps are consistent with legitimate build output.	ai	2026/04/24
bogus-package	bogus-package	AI (bogus-package): chancestrickland is the legitimate Reach UI maintainer with 1790 approved packages; spam flag is a false positive. No keywords is trivial.	ai	2026/04/24
npm-metadata	suspicious-initial-version	AI (npm-metadata): @reach/* packages commonly use 0.0.0 as initial version in their monorepo publishing pattern; publisher is well-established with a long track record.	ai	2026/04/24
email-domain	unclaimed-email:ryanflorence	AI (email-domain): The 'email' field contains '@ryanflorence' which is a Twitter handle, not a real email address with a domain. No actual domain hijacking risk applies here.	ai	2026/04/24
phantom-deps	phantom-dep:@reach/portal	AI (phantom-deps): @reach/portal is a same-org scoped dependency; phantom detection is a false positive for intra-monorepo packages in the @reach ecosystem.	ai	2026/04/24

Versions (showing 51 of 55)

View all versions

Version	Deps	Published
0.18.0	6 / 8	2022-10-13
0.17.0	8 / 3	2022-04-20
0.16.5	8 / 3	2021-12-06
0.16.4	8 / 3	2021-11-16
0.16.3	7 / 3	2021-10-19
0.16.2	7 / 3	2021-10-17
0.16.1	7 / 3	2021-08-02
0.16.0	7 / 3	2021-08-02
0.15.3	7 / 3	2021-07-10
0.15.2	7 / 3	2021-06-28
0.15.1	7 / 3	2021-04-20
0.15.0	8 / 2	2021-04-07
0.14.0	8 / 2	2021-03-28
0.13.2	8 / 2	2021-02-21
0.13.1	8 / 2	2021-02-21
0.13.0	8 / 0	2021-01-26
0.12.1	8 / 0	2020-11-27
0.12.0	8 / 0	2020-11-26
0.11.2	8 / 0	2020-09-01
0.11.1	8 / 0	2020-09-01
0.11.0	8 / 0	2020-08-21
0.10.5	8 / 0	2020-06-24
0.10.4	8 / 0	2020-06-15
0.10.3	8 / 0	2020-05-21
0.10.2	8 / 0	2020-05-11
0.10.1	8 / 0	2020-04-22
0.10.0	8 / 0	2020-04-05
0.9.1	9 / 0	2020-03-19
0.9.0	9 / 0	2020-03-14
0.8.6	9 / 0	2020-03-06
0.8.5	9 / 0	2020-02-21
0.8.4	9 / 0	2020-02-15
0.8.3	9 / 0	2020-02-15
0.8.2	9 / 0	2020-02-08
0.8.0	7 / 0	2020-01-30
0.7.4	7 / 0	2020-01-25
0.7.3	7 / 0	2020-01-17
0.7.2	7 / 0	2020-01-10
0.7.1	7 / 0	2020-01-09
0.7.0	7 / 0	2019-12-22
0.6.4	7 / 0	2019-12-10
0.6.2	7 / 0	2019-11-23
0.6.1	7 / 4	2019-11-15
0.5.3	7 / 4	2019-11-04
0.5.0	7 / 4	2019-10-31
0.4.0	7 / 4	2019-10-23
0.3.0	7 / 4	2019-10-11
0.1.1	6 / 5	2019-06-19
0.1.0	6 / 5	2019-06-07
0.0.5	6 / 5	2019-06-07
0.0.4	6 / 5	2019-06-06

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

1 finding

LOW No provenance attestation provenance

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

v0.16.4

1 finding

LOW No provenance attestation provenance

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

v0.16.3

1 finding

LOW No provenance attestation provenance

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

v0.16.2

2 findings

HIGH Publisher changed: mjackson → chancestrickland (on 2021-10-17) provenance

This version was published by a different npm account than previous versions on 2021-10-17. 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.16.1

2 findings

HIGH Publisher changed: mjackson → chancestrickland (on 2021-08-02) provenance

This version was published by a different npm account than previous versions on 2021-08-02. 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.16.0

2 findings

HIGH Publisher changed: mjackson → chancestrickland (on 2021-08-02) provenance

This version was published by a different npm account than previous versions on 2021-08-02. 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.15.3

2 findings

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

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.

LOW No provenance attestation provenance

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

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

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

1 finding

LOW No provenance attestation provenance

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

v0.12.1

1 finding

LOW No provenance attestation provenance

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

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

1 finding

LOW No provenance attestation provenance

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

v0.8.2

1 finding

LOW No provenance attestation provenance

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

v0.8.0

1 finding

LOW No provenance attestation provenance

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

v0.7.4

1 finding

LOW No provenance attestation provenance

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

v0.7.3

1 finding

LOW No provenance attestation provenance

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

v0.7.2

1 finding

LOW No provenance attestation provenance

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

v0.7.1

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

HIGH Publisher changed: mjackson → chancestrickland (on 2020-01-09) provenance

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

1 finding

LOW No provenance attestation provenance

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

v0.6.4

1 finding

LOW No provenance attestation provenance

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

v0.6.2

1 finding

LOW No provenance attestation provenance

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

v0.6.1

1 finding

LOW No provenance attestation provenance

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

v0.5.3

1 finding

LOW No provenance attestation provenance

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

v0.5.0

1 finding

LOW No provenance attestation provenance

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

v0.4.0

2 findings

HIGH Publisher changed: ryanflorence → mjackson (on 2019-10-23) provenance

This version was published by a different npm account than previous versions on 2019-10-23. 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.3.0

2 findings

HIGH Publisher changed: ryanflorence → mjackson (on 2019-10-11) provenance

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

1 finding

LOW No provenance attestation provenance

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

v0.1.0

1 finding

LOW No provenance attestation provenance

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

v0.0.5

1 finding

LOW No provenance attestation provenance

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

v0.0.4

1 finding

LOW No provenance attestation provenance

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