anuraghazra/gatsby
stale
significant_divergence
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.
TylerBarnes/gatsby
stale
significant_divergence
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.
janiceilene/gatsby
stale
significant_divergence
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.
nubank/gatsby
stale
significant_divergence
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.
vision03111/GATSBY_PROJECT
stale
significant_divergence
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.
vasrush/gatsby
stale
significant_divergence
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.
patrickm68/gatsby
stale
significant_divergence
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.
j-j-gajjar/gatsby
stale
significant_divergence
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.
Developerayo/gatsby
stale
significant_divergence
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.
sdras/gatsby
stale
significant_divergence
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.