← Home

@gatsbyjs/reach-router

npm Repository Homepage

Gatsby's fork to modernize reach-router

7
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

smcgaritykathmbecknodebotanistj0sh77mcolelittletyhoppkgarbayamarvinjudehkkylemathewsdschaupiehwardpeettylerbarnesfksmthomaslekoartsdmccrawjulienprachelbahldaniellewgatsbymlgualtieri-gatsbygatsby_integrations

Keywords

reactreach routergatsby

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:react-router AI (typosquat): Scoped under @gatsbyjs org — a legitimate Gatsby-maintained fork of @reach/router. Not a typosquat of react-router; the Levenshtein match is a mechanical false positive for this well-known package. ai
bogus-package bogus-package AI (bogus-package): Inflated semver reflects intentional version alignment with upstream @reach/router fork. README link dump is consistent with a documentation-heavy router library. Not a spam/phishing package. ai
source-diff obfuscated-file:dist/index.js AI (source-diff): Standard microbundle minified output. Code samples show recognizable React router logic (history API, pushState, URL parsing). Not malicious obfuscation. ai
source-diff source-size-dropped AI (source-diff): Size drop explained by removal of react-lifecycles-compat runtime dep and modernization to React 18. Legitimate refactor, not code replacement with a stub. ai
source-diff obfuscated-file:dist/index.modern.mjs AI (source-diff): Standard microbundle minified ESM output. Code samples show recognizable React router logic. Not malicious obfuscation. ai
install-scripts install-script:postinstall AI (install-scripts): Script is named '_postinstall' (underscore prefix) so npm does not execute it. It's a husky dev-tool pattern to prevent consumer execution; stable false positive for this package. ai
provenance publisher-changed AI (provenance): Publisher change from lekoarts to pieh reflects an internal Gatsby team transition; both are known Gatsby contributors. This is stable for this package. ai
maintainer-change maintainer-removed AI (maintainer-change): Removal of abhiaiyer is consistent with routine Gatsby org team changes; no indication of hostile takeover given publisher's strong track record. ai

Versions (showing 7 of 7)

Version Deps Published
2.0.1 2 / 17
2.0.0 2 / 18
1.3.9 3 / 34
1.3.8 3 / 34
1.3.7 3 / 34
1.3.6 3 / 34
1.3.5 3 / 34

v2.0.1

2 findings
HIGH Publisher changed: lekoarts → pieh (on 2023-01-27) provenance

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

v2.0.0

4 findings
HIGH Package has 'postinstall' script install-scripts

Script: husky install

HIGH New obfuscated file: dist/index.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: dist/index.modern.mjs source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v1.3.9

1 finding
LOW No provenance attestation provenance

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

v1.3.8

1 finding
LOW No provenance attestation provenance

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

v1.3.7

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: pieh → lekoarts (on 2022-04-05) provenance

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

v1.3.6

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: wardpeet → pieh (on 2021-03-03) provenance

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

v1.3.5

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'react-router' typosquat

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

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.