@reach/rect — Greenflagged

Measure React elements position in the DOM

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
typosquat	typosquat.levenshtein:react	AI (typosquat): @reach/rect is a legitimate Reach UI package; 'rect' means rectangle (getBoundingClientRect), not a typo of 'react'. Published by ryanflorence under the established @reach scope.	ai	2026/04/24
typosquat	typosquat.levenshtein:jest	AI (typosquat): @reach/rect is a legitimate scoped package; Levenshtein match to 'jest' is purely coincidental.	ai	2026/04/24
typosquat	typosquat.levenshtein:next	AI (typosquat): @reach/rect is a legitimate scoped package; Levenshtein match to 'next' is purely coincidental.	ai	2026/04/24
provenance	missing-githead	AI (provenance): Reach UI monorepo likely changed publish tooling; chancestrickland is a long-standing maintainer with strong track record.	ai	2026/04/24
bogus-package	bogus-package	AI (bogus-package): chancestrickland has 1794 approved versions across 83 packages; spam flag is a false positive for this publisher.	ai	2026/04/24
email-domain	unclaimed-email:ryanflorence	AI (email-domain): The 'email' field contains a Twitter handle (@ryanflorence), not a real email address. Not an exploitable domain hijack vector.	ai	2026/04/24
publish-pattern	new-deps-added	AI (publish-pattern): prop-types is the canonical React prop validation library from the React team; adding it to a React UI component is entirely expected and benign.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): mjackson is the co-founder of the same org as ryanflorence; this is a known legitimate maintainer transition within the @reach/* ecosystem.	ai	2026/04/24
provenance	publisher-changed	AI (provenance): ryanflorence and mjackson are co-founders of the same org (Remix/React Training) and co-maintainers of the entire @reach/* ecosystem. This transition is legitimate and stable.	ai	2026/04/24

Versions (showing 42 of 42)

Version	Deps	Published
0.18.0	2 / 6	2022-10-13
0.17.0	5 / 2	2022-04-20
0.16.0	5 / 2	2021-08-02
0.15.3	5 / 2	2021-07-10
0.15.2	5 / 2	2021-06-28
0.15.0	5 / 2	2021-04-07
0.14.0	4 / 2	2021-03-28
0.13.2	4 / 2	2021-02-21
0.13.1	4 / 2	2021-02-21
0.13.0	4 / 0	2021-01-26
0.12.1	4 / 0	2020-11-27
0.12.0	4 / 0	2020-11-26
0.11.2	4 / 0	2020-09-01
0.11.1	4 / 0	2020-09-01
0.11.0	4 / 0	2020-08-21
0.10.5	4 / 0	2020-06-24
0.10.4	4 / 0	2020-06-15
0.10.3	4 / 0	2020-05-21
0.10.2	4 / 0	2020-05-11
0.10.1	4 / 0	2020-04-22
0.10.0	4 / 0	2020-04-05
0.9.0	4 / 0	2020-03-14
0.8.6	4 / 0	2020-03-06
0.8.2	3 / 0	2020-02-08
0.8.0	2 / 0	2020-01-30
0.7.4	2 / 0	2020-01-25
0.7.3	2 / 0	2020-01-17
0.7.2	2 / 0	2020-01-10
0.7.1	2 / 0	2020-01-09
0.7.0	2 / 0	2019-12-22
0.6.2	2 / 0	2019-11-23
0.6.1	2 / 0	2019-11-15
0.5.0	2 / 0	2019-10-31
0.4.0	2 / 0	2019-10-23
0.3.0	3 / 0	2019-10-11
0.2.1	2 / 0	2019-04-20
0.2.0	2 / 0	2019-03-18
0.1.2	2 / 0	2019-01-29
0.1.1	2 / 0	2018-09-03
0.1.0	2 / 0	2018-08-29
0.0.2	2 / 0	2018-07-31
0.0.1	2 / 0	2018-07-31

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

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

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 2020-01-09) provenance

[Accepted risk] 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.

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

1 finding

LOW No provenance attestation provenance

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

v0.3.0

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

HIGH Unclaimed maintainer email domain: ryanflorence email-domain

Maintainer email '@ryanflorence' uses domain 'ryanflorence' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

LOW No provenance attestation provenance

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

v0.2.1

1 finding

LOW No provenance attestation provenance

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

v0.2.0

1 finding

LOW No provenance attestation provenance

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

v0.1.2

1 finding

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

1 finding

LOW No provenance attestation provenance

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

v0.0.1

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'react' typosquat

Package name '@reach/rect' is 1 edit(s) away from popular package 'react'.

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.