murilothink/github-readme-stats
stale
significant_divergence
Selected Choose this fork only if you need its specific historical customizations and are prepared to maintain it yourself. For most adopters, upstream is the safer default because this fork is far behind and likely missing newer fixes and features.
stats-organization/github-stats-extended
active
significant_divergence
Prefer this fork if you want a more productized, configurable stats platform with app structure and private/login-oriented workflows. Stay with upstream if you want the simplest, most battle-tested readme-card generator with minimal divergence and easier compatibility.
DenverCoder1/github-readme-stats
stale
significant_divergence
Choose this fork if you want a customized, localization-friendly variant and are willing to own merge debt. Choose upstream if you want the freshest fixes, lower maintenance risk, and the most current deployment/tooling support.
KKPRO2007/github-readme-stats
Choose upstream unless you specifically want this fork identity or a starting point for your own edits. It offers no evident feature upside, and it trails upstream by one commit.
stats-organization/github-readme-stats
Choose this fork if you want upstream compatibility with incremental improvements to translations, language-card customization, and supporting workflows. If you need major new card types or a broad product shift, upstream is likely the better baseline.
idkwuu/github-readme-stats
slowing
significant_divergence
Choose this fork if you specifically want a customized, cost-optimized, cache-friendly variant with translated docs and you are comfortable owning a large upstream gap. Choose upstream if you want the latest maintained behavior, CI, and compatibility with minimal merge risk.
farhan7reza7/github-readme-stats
stale
significant_divergence
Choose this fork only if localization or fork-specific documentation is the main value. If you want the latest upstream features, fixes, and maintenance, the upstream repo is the safer default.
Ahtisham-1214/github-readme-stats
Choose this fork only if the added theme is specifically useful to you. If you want the broadest feature set and freshest maintenance, upstream is the better default; this fork is mainly for narrow theme customization.
JuyaoHuang/github-readme-stats
Choose upstream unless you specifically need this exact fork identity; it does not show added capabilities and is already behind recent upstream maintenance.
Nekonify/github-readme-stats
stale
significant_divergence
Choose this fork only if you specifically want its older customizations and are prepared to own maintenance. For most adopters, upstream is the better default because it is active, better tested, and substantially ahead on fixes and workflow support.