/jump to repo

Repos Recent Bookmarks Watched Notes Tags Discover Compare Stats GitHub

Repository brief

gatsbyjs/gatsby

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis

cached 2026-03-30T11:44:50.777Z

3mo ago

gatsbyjs/gatsby

gatsbyjs/gatsby is a large, active open source React-based framework for building fast websites and apps. It is not archived, has a very large fork and star count, and shows recent maintenance activity as of 2026-03-30.

Loading tags...

Stars55,954

Forks10,212

Default branchmaster

Last pushed2026-03-30T11:18:26Z

Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs

Maintenance:

Magnitude:

Sort:

Selected

Prefer this fork only if you want its starter/dependency snapshot and can accept significant upstream lag. For most adopters, upstream Gatsby is the safer choice because this fork is stale and heavily diverged.

Prefer this fork only if you need the WordPress-experimental extraction and are prepared to maintain a long-lived, highly diverged snapshot. For general Gatsby usage, upstream is the better choice.

Choose this fork only if you specifically need a frozen legacy Gatsby branch or its custom starter/docs/workflow changes. For new work or anything that benefits from current Gatsby capabilities, upstream is the better choice.

Prefer this fork if you need a frozen, internally curated Gatsby distribution with reproducible installs and custom benchmark/test artifacts. Prefer upstream if you want active maintenance, newer fixes, and the broadest plugin/starter ecosystem.

Prefer the fork only if you specifically need its older experimental Gatsby changes and are prepared to maintain the divergence. For most adopters, upstream is the safer choice because it is active, current, and much better supported.

Choose upstream unless you specifically need this older fork’s exact state. This fork looks more like a frozen, divergent maintenance branch than a better-supported alternative, so it is a poor default for new adoption.

Choose this fork only if you need its older pinned behavior or its starter/WordPress-oriented customizations. For most adopters, upstream Gatsby is the better choice because it is active, more current, and lower-risk to maintain.

Prefer upstream unless you specifically need this older 2021 snapshot. The fork looks stale, materially diverged, and likely expensive to maintain, but it may still be useful as a legacy baseline for starter-heavy or WordPress-related workflows.

Choose this fork only if you need its specific 2020-era content and starter customizations. For most adopters, upstream is the better default because it is active, maintained, and far ahead in dependency and framework support.

Prefer this fork only if its legacy docs/starter/CMS customization is the asset you want. For anything greenfield or actively maintained, upstream Gatsby is the safer choice because this fork is materially stale and far behind current framework work.

Fork comparison

anuraghazra/gatsby

38/100

stale

significant_divergence

Prefer this fork only if you want its starter/dependency snapshot and can accept significant upstream lag. For most adopters, upstream Gatsby is the safer choice because this fork is stale and heavily diverged.

Likely purpose

To maintain a customized Gatsby distro focused on starter templates, dependency pinning/updates, and some CI/build workflow tweaks.

Best for

Teams intentionally maintaining an older Gatsby baseline.; Developers who want a customized set of Gatsby starters rather than the latest framework.; Users prioritizing stability and local tweaks over upstream feature velocity.; People willing to own long-term maintenance and manual upstream backports.

Additional features

Updated starter-template dependency sets and lockfiles across multiple starters, which suggests a curated app/starter baseline.
Renovate-driven dependency automation for starter packages and repo tooling.
Build and job-observability workflow tweaks from older upstream commits, including pending-job logging and job activity handling.
Node manifest API v2 support in the forked history, which would matter for build/deployment workflows.
Expands API, schema, or SDK surface area for downstream integrations and generated clients.
Introduces more operational workflow surface such as server-side handling, auth, session control, or admin tooling.

Missing features

It is far behind upstream Gatsby, so it likely lacks many recent framework fixes, dependency updates, and security patches.
Recent upstream starter, docs, and tooling improvements from 2026 are not present here.
Current upstream maintenance cadence and active release alignment are absent, making upgrades and compatibility harder.
Upstream additions beyond the fork point, such as later framework/runtime and ecosystem changes, are likely missing.
It trails upstream by 200 commits, so some recent upstream features and fixes are likely not present yet.

Strengths

Could be useful as a frozen, opinionated Gatsby baseline for teams that want stability over upstream churn.
Starter-centric changes make it potentially practical for bootstrapping projects with locked dependency sets.
May already include workflow conveniences around dependency updates and build troubleshooting.

Risks

Materially stale relative to upstream, with a 607-day gap since the fork last pushed.
Very large bidirectional divergence makes rebasing or cherry-picking upstream fixes expensive.
Dependency lockfile churn suggests the fork may be hard to reproduce or maintain consistently.
Users adopting it inherit older Gatsby assumptions and may hit incompatibilities with modern packages or hosting workflows.