react-router-hash-link MIT 22 versions

react-router-hash-link

npm Repository Homepage

Hash link scroll functionality for React Router v4/5

22

Versions

MIT

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

rafgraph

Keywords

reactreact-routerlinkhash-linkscroll

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	no-provenance	AI (provenance): Long-established package with clean history; lack of Sigstore provenance is a best-practice gap, not a security risk for this package.	ai	2026/04/24
provenance	publisher-changed	AI (provenance): The rafrex→rafgraph change is a documented account rename by the same author (Rafael Pedicini); repo URL and author email both reflect rafgraph identity consistently.	ai	2026/04/24
maintainer-change	maintainer-takeover	AI (maintainer-change): rafrex and rafgraph are the same author (Rafael Pedicini); the repo URL and author email both reference rafgraph.dev. This is an account rename, not a hostile takeover.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): New maintainer rafgraph is the same person as rafrex (account rename); no new third party was added.	ai	2026/04/24
maintainer-change	maintainer-removed	AI (maintainer-change): rafrex was removed because the author renamed their account to rafgraph; not a hostile removal.	ai	2026/04/24

Versions (showing 22 of 22)

Version	Deps	Published
2.4.3	1 / 6	2021-05-13
2.4.2	1 / 6	2021-05-13
2.4.1	1 / 6	2021-05-04
2.4.0	1 / 1	2021-02-11
2.3.1	1 / 5	2020-12-09
2.3.0	1 / 5	2020-12-09
2.2.2	1 / 5	2020-10-10
2.2.1	1 / 5	2020-10-10
2.2.0	1 / 5	2020-10-09
2.1.0	1 / 4	2020-09-11
2.0.0	1 / 4	2020-07-14
1.2.2	1 / 4	2019-07-20
1.2.1	1 / 4	2018-11-05
1.2.0	1 / 4	2018-02-17
1.1.1	1 / 4	2017-09-26
1.1.0	1 / 4	2017-04-29
1.0.0	0 / 4	2017-04-02
0.3.1	0 / 4	2017-04-01
0.3.0	0 / 4	2017-03-30
0.2.1	0 / 4	2017-03-14
0.2.0	0 / 4	2017-03-14
0.1.0	0 / 4	2017-03-14

v2.4.3

1 finding

LOW No provenance attestation provenance

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

v2.4.2

1 finding

LOW No provenance attestation provenance

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

v2.4.1

1 finding

LOW No provenance attestation provenance

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

v2.4.0

1 finding

LOW No provenance attestation provenance

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

v2.3.1

1 finding

LOW No provenance attestation provenance

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

v2.3.0

1 finding

LOW No provenance attestation provenance

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

v2.2.2

1 finding

LOW No provenance attestation provenance

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

v2.2.1

1 finding

LOW No provenance attestation provenance

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

v2.2.0

1 finding

LOW No provenance attestation provenance

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

v2.1.0

2 findings

HIGH Complete maintainer takeover detected maintainer-change

All previous maintainers (rafrex) were replaced by new maintainers (rafgraph). This is a strong signal of a potential package hijack and requires careful review.

LOW No provenance attestation provenance

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

v2.0.0

2 findings

HIGH Publisher changed: rafrex → rafgraph (on 2020-07-14) provenance

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

v1.2.2

1 finding

LOW No provenance attestation provenance

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

v1.2.1

1 finding

LOW No provenance attestation provenance

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

v1.2.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: rafrex.

LOW No provenance attestation provenance

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

v1.1.1

1 finding

LOW No provenance attestation provenance

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

v1.1.0

1 finding

LOW No provenance attestation provenance

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

v1.0.0

1 finding

LOW No provenance attestation provenance

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