gatsby-plugin-catch-links
Intercepts local links from markdown and other non-react pages and does a client-side pushState to avoid the browser having to refresh the page.
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): pieh is a known Gatsby core team member with 6205 approved packages; this is a legitimate internal team transition within the gatsbyjs org, not a compromise. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainer kathmbeck is consistent with Gatsby team operations; package is part of the official gatsbyjs/gatsby monorepo with no suspicious code changes. | ai | |
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): @babel/runtime is injected by Babel transpilation in Gatsby plugins; not directly imported but legitimately used. Stable pattern for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Mass-production flag reflects pieh's role as Gatsby monorepo maintainer; empty index.js is standard for Gatsby plugins that build output via prepare script. Not indicative of spam. | ai |
Versions (showing 100 of 158)
| Version | Deps | Published |
|---|---|---|
| 5.16.0 | 2 / 4 | |
| 5.15.0 | 2 / 4 | |
| 5.14.0 | 2 / 4 | |
| 5.13.1 | 2 / 4 | |
| 5.13.0 | 2 / 4 | |
| 5.12.0 | 2 / 4 | |
| 5.11.0 | 2 / 4 | |
| 5.10.0 | 2 / 4 | |
| 5.9.0 | 2 / 4 | |
| 5.8.0 | 2 / 4 | |
| 5.7.0 | 2 / 4 | |
| 5.6.0 | 2 / 4 | |
| 5.5.0 | 2 / 4 | |
| 5.4.0 | 2 / 4 | |
| 5.3.0 | 2 / 4 | |
| 5.2.0 | 2 / 4 | |
| 5.1.0 | 2 / 4 | |
| 5.0.0 | 2 / 4 | |
| 4.25.0 | 2 / 4 | |
| 4.24.0 | 2 / 4 | |
| 4.23.0 | 2 / 4 | |
| 4.22.0 | 2 / 4 | |
| 4.21.0 | 2 / 4 | |
| 4.20.0 | 2 / 4 | |
| 4.19.0 | 2 / 4 | |
| 4.18.0 | 2 / 4 | |
| 4.17.0 | 2 / 4 | |
| 4.16.0 | 2 / 4 | |
| 4.15.0 | 2 / 4 | |
| 4.14.0 | 2 / 4 | |
| 4.13.0 | 2 / 4 | |
| 4.12.1 | 2 / 4 | |
| 4.12.0 | 2 / 4 | |
| 4.11.0 | 2 / 4 | |
| 4.10.0 | 2 / 4 | |
| 4.9.0 | 2 / 4 | |
| 4.8.0 | 2 / 4 | |
| 4.7.0 | 2 / 4 | |
| 4.6.0 | 2 / 4 | |
| 4.5.0 | 2 / 4 | |
| 4.4.0 | 2 / 4 | |
| 4.3.0 | 2 / 4 | |
| 4.2.0 | 2 / 4 | |
| 4.1.0 | 2 / 4 | |
| 4.0.0 | 2 / 4 | |
| 3.15.0 | 2 / 4 | |
| 3.14.0 | 2 / 4 | |
| 3.13.0 | 2 / 4 | |
| 3.12.0 | 2 / 4 | |
| 3.11.0 | 2 / 4 | |
| 3.10.0 | 2 / 4 | |
| 3.9.0 | 2 / 4 | |
| 3.8.0 | 2 / 4 | |
| 3.7.1 | 2 / 4 | |
| 3.7.0 | 2 / 4 | |
| 3.6.0 | 2 / 4 | |
| 3.5.0 | 2 / 4 | |
| 3.4.0 | 2 / 4 | |
| 3.3.0 | 2 / 4 | |
| 3.2.0 | 2 / 4 | |
| 3.1.0 | 2 / 4 | |
| 3.0.0 | 2 / 4 | |
| 2.10.0 | 2 / 4 | |
| 2.9.0 | 2 / 4 | |
| 2.8.0 | 2 / 4 | |
| 2.7.0 | 2 / 4 | |
| 2.6.0 | 2 / 4 | |
| 2.5.0 | 2 / 4 | |
| 2.4.0 | 2 / 4 | |
| 2.3.15 | 2 / 4 | |
| 2.3.14 | 2 / 4 | |
| 2.3.13 | 2 / 4 | |
| 2.3.12 | 2 / 4 | |
| 2.3.11 | 2 / 4 | |
| 2.3.10 | 2 / 4 | |
| 2.3.9 | 2 / 4 | |
| 2.3.7 | 2 / 4 | |
| 2.3.6 | 2 / 4 | |
| 2.3.5 | 2 / 4 | |
| 2.3.4 | 2 / 4 | |
| 2.3.3 | 2 / 4 | |
| 2.3.2 | 2 / 4 | |
| 2.3.1 | 2 / 4 | |
| 2.3.0 | 2 / 4 | |
| 2.2.4 | 2 / 4 | |
| 2.2.3 | 2 / 4 | |
| 2.2.2 | 2 / 4 | |
| 2.2.1 | 2 / 4 | |
| 2.2.0 | 2 / 4 | |
| 2.1.28 | 2 / 4 | |
| 2.1.27 | 2 / 4 | |
| 2.1.26 | 2 / 4 | |
| 2.1.25 | 2 / 4 | |
| 2.1.24 | 2 / 4 | |
| 2.1.23 | 2 / 4 | |
| 2.1.21 | 2 / 4 | |
| 2.1.19 | 2 / 4 | |
| 2.1.18 | 2 / 4 | |
| 2.1.17 | 2 / 4 | |
| 2.1.16 | 2 / 4 |
v5.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.14.0
2 findingsThis version was published by a different npm account than previous versions on 2024-11-06. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.12.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2023-08-24. This could indicate a legitimate maintainer transition or an account compromise.
v5.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.0
2 findingsThis version was published by a different npm account than previous versions on 2023-04-18. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2023-02-21. This could indicate a legitimate maintainer transition or an account compromise.
v5.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.0
2 findingsThis version was published by a different npm account than previous versions on 2023-01-24. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2023-01-10. This could indicate a legitimate maintainer transition or an account compromise.
v5.3.0
2 findingsThis version was published by a different npm account than previous versions on 2022-12-13. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-11-25. This could indicate a legitimate maintainer transition or an account compromise.
v5.1.0
2 findingsThis version was published by a different npm account than previous versions on 2022-11-22. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
2 findingsThis version was published by a different npm account than previous versions on 2022-11-08. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.24.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-09-27. This could indicate a legitimate maintainer transition or an account compromise.
v4.23.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-09-13. This could indicate a legitimate maintainer transition or an account compromise.
v4.22.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-08-30. This could indicate a legitimate maintainer transition or an account compromise.
v4.21.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-08-16. This could indicate a legitimate maintainer transition or an account compromise.
v4.20.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-08-02. This could indicate a legitimate maintainer transition or an account compromise.
v4.19.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-07-19. This could indicate a legitimate maintainer transition or an account compromise.
v4.18.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-07-05. This could indicate a legitimate maintainer transition or an account compromise.
v4.17.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-06-21. This could indicate a legitimate maintainer transition or an account compromise.
v4.16.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-06-07. This could indicate a legitimate maintainer transition or an account compromise.
v4.15.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-05-24. This could indicate a legitimate maintainer transition or an account compromise.
v4.14.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-05-10. This could indicate a legitimate maintainer transition or an account compromise.
v4.13.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-04-26. This could indicate a legitimate maintainer transition or an account compromise.
v4.12.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-04-12. This could indicate a legitimate maintainer transition or an account compromise.
v4.12.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-04-12. This could indicate a legitimate maintainer transition or an account compromise.
v4.11.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-03-29. This could indicate a legitimate maintainer transition or an account compromise.
v4.10.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-03-16. This could indicate a legitimate maintainer transition or an account compromise.
v4.9.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-03-01. This could indicate a legitimate maintainer transition or an account compromise.
v4.8.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-02-22. This could indicate a legitimate maintainer transition or an account compromise.
v4.7.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-02-08. This could indicate a legitimate maintainer transition or an account compromise.
v4.6.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-01-25. This could indicate a legitimate maintainer transition or an account compromise.
v4.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2021-12-14. This could indicate a legitimate maintainer transition or an account compromise.
v4.3.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2021-12-01. This could indicate a legitimate maintainer transition or an account compromise.
v4.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2021-11-02. This could indicate a legitimate maintainer transition or an account compromise.
v4.0.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2021-10-21. This could indicate a legitimate maintainer transition or an account compromise.