tldr-pages/tldr

Prefer upstream unless you specifically want this fork’s translation and maintenance automation. Adopt this fork only if its custom editorial workflow is the point and you are willing to absorb the sync burden.

Prefer upstream unless you explicitly need this fork’s legacy snapshot or custom alias/translation workflow. For most adopters, the fork is too stale and too diverged to be a good base.

Prefer upstream unless you specifically need this older customized documentation workflow or a frozen snapshot; for normal cheat-sheet usage, this fork is too stale and too divergent.

Prefer upstream for current coverage and community maintenance. Choose this fork only if you need a customized or frozen documentation workflow and can accept substantial staleness and merge debt.

Choose this fork only if you want an older, highly customized tldr maintenance base. If you want current command coverage and upstream momentum, upstream is the better default.

Prefer upstream unless you specifically need this older fork's custom translation/alias workflow or historical snapshot. For normal cheat-sheet use, this fork is too stale and too divergent to be a safe adoption target.

Prefer upstream unless you specifically want this fork’s older translation and alias-page workflow. Choose this fork only if the divergence itself is the point; otherwise it is too stale to be a practical replacement.

Prefer upstream unless you specifically need this fork's custom translation and maintenance workflow; otherwise it is too stale and too far diverged to be a low-risk drop-in replacement.

Prefer upstream unless you explicitly need this old snapshot or its custom alias/translation workflow. For almost everyone else, the fork is too stale and too far behind to be a good adoption target.