Discofork
Repository brief

anuraghazra/github-readme-stats

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-30T12:53:18.092Z
3mo ago

anuraghazra/github-readme-stats

Highly popular Node.js/JavaScript project that generates dynamic GitHub profile/readme stats cards. It is active, non-archived, and heavily forked/starred, which makes forks potentially interesting if they add new card types, themes, or behavior around stat rendering and deployment. The repo appears production-oriented with tests, linting, CI, and Vercel deployment support.

GitHub
Loading tags...
Stars78,923
Forks31,842
Default branchmaster
Last pushed2026-03-20T00:28: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
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.

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.

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.

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.

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.

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.

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.

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.

Choose upstream unless you specifically need this exact fork identity; it does not show added capabilities and is already behind recent upstream maintenance.

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.