bep/hugo
stale
significant_divergence
Selected Choose this fork only if its custom packaging or local behavior is the point. If you mainly want Hugo itself, upstream is the safer choice because this fork is far behind and heavily diverged.
graemephi/kahugo
stale
significant_divergence
Choose this fork only if you already depend on its custom behavior and can absorb the maintenance cost. For most new adopters, upstream Hugo is the better choice because this fork is old, materially divergent, and likely missing many current capabilities and fixes.
satya-nutella/hugo
stale
significant_divergence
Prefer this fork only if you specifically need its older custom behavior and are prepared to maintain it yourself. For most adopters, upstream Hugo is the better choice because this fork is materially stale and highly divergent.
huo-ju/hugo
stale
significant_divergence
Choose this fork only if you need its legacy publish/taxonomy behavior and can tolerate a long-unmaintained codebase. For new work or active sites, upstream Hugo is the safer choice.
SchumacherFM/hugo
stale
significant_divergence
Prefer upstream unless you specifically need this fork's custom deployment or packaging changes. This fork looks like a maintenance-heavy, long-diverged variant that is useful for niche operational workflows, but it is not a good choice if you want current Hugo features and low upgrade friction.
fastai/hugo
stale
significant_divergence
Choose this fork only if you need its existing custom docs/example-site behavior and can live with a very old Hugo base. For new work or active maintenance, upstream is the better default.
SDLMoe/hugo
stale
significant_divergence
Prefer this fork only if you need its existing internal customizations and are willing to own a long-term divergence from upstream. If you want a current, well-supported Hugo with the broadest feature set, upstream is the safer choice.
chisa-dev/hugo
stale
significant_divergence
Prefer this fork only if you specifically need its older, customized behavior and are willing to own ongoing maintenance. For new work or for teams that want current Hugo capabilities, upstream is the safer choice.
TAIPANBOX/hugo
stale
significant_divergence
Choose this fork only if you need its legacy behavior and can accept being years behind upstream. For new sites or active maintenance, upstream Hugo is the safer choice; this fork is mainly for compatibility-driven holdouts.
Vonng/hugo
stale
significant_divergence
Choose this fork only if its math/documentation-specific behavior is the point. For most adopters, upstream Hugo is the better default because this fork is heavily outdated and likely missing many modern capabilities and fixes.