@reach/portal — Greenflagged

Declarative portals for React

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
email-domain	unclaimed-email:ryanflorence	AI (email-domain): Ryan Florence uses his Twitter handle (@ryanflorence) as a placeholder email across all his packages — not a real domain. This is a known stylistic choice, not a hijackable email domain.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): mjackson (Michael Jackson) is the co-author of Reach UI alongside Ryan Florence. This addition is a legitimate co-maintainer transition, not a suspicious takeover.	ai	2026/04/24
bogus-package	bogus-package	AI (bogus-package): chancestrickland is the legitimate Reach UI maintainer with 1780 approved packages; spam flag is a false positive.	ai	2026/04/24
provenance	publisher-changed	AI (provenance): chancestrickland is the documented successor maintainer of the Reach UI monorepo; this transition from mjackson is legitimate and stable across all @reach/* packages.	ai	2026/04/24
phantom-deps	phantom-dep:tslib	AI (phantom-deps): tslib is explicitly declared as a runtime dependency in package.json; it is a standard TypeScript helper and its use as an implicit dep is expected for this build setup.	ai	2026/04/24

Versions (showing 45 of 45)

Version	Deps	Published
0.18.0	1 / 6	2022-10-13
0.17.0	3 / 2	2022-04-20
0.16.2	3 / 2	2021-10-17
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.0	2 / 0	2020-03-14
0.8.6	2 / 0	2020-03-06
0.8.5	1 / 0	2020-02-21
0.8.2	1 / 0	2020-02-08
0.8.0	0 / 0	2020-01-30
0.7.4	0 / 0	2020-01-25
0.7.3	0 / 0	2020-01-17
0.7.2	0 / 0	2020-01-10
0.7.1	0 / 0	2020-01-08
0.7.0	0 / 0	2019-12-22
0.6.2	1 / 0	2019-11-23
0.6.1	1 / 0	2019-11-15
0.5.0	1 / 0	2019-10-31
0.4.0	1 / 0	2019-10-23
0.3.0	1 / 0	2019-10-11
0.2.1	1 / 0	2019-04-29
0.2.0	1 / 0	2019-04-20
0.1.3	1 / 0	2019-03-18
0.1.2	1 / 0	2019-01-29
0.1.1	1 / 0	2018-09-03
0.1.0	1 / 0	2018-08-29
0.0.2	1 / 0	2018-07-31
0.0.1	1 / 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.2

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

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

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

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-01-10) provenance

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

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-08) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2020-01-08. 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 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.

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

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

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

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

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.