Textualize/rich

Prefer upstream unless you specifically need an old frozen snapshot. This fork shows no added functionality, but it is far behind current Rich and therefore carries maintenance and bug-fix risk.

Prefer upstream unless you explicitly need an old frozen snapshot. This fork adds no visible functionality and is materially behind, so it is mainly for archival or reproducibility use cases.

Prefer upstream for almost any real use. This fork looks like an abandoned snapshot with no added capabilities and a very large upstream gap, so it is only sensible if you specifically need the 2022-era baseline.

Choose upstream unless you specifically need a frozen snapshot. This fork adds no visible features and is far behind upstream, so it is best treated as stale reference material rather than a maintained alternative.

Prefer the upstream project unless you specifically need this fork’s benchmark/reporting customization or local README/workflow changes. For general Rich adoption, the fork is too stale and too far behind upstream to be the safer default.

Prefer upstream unless you specifically need this fork’s older custom behavior. This fork is materially behind and likely harder to maintain, but it may be useful as a frozen, customized Rich variant.

Prefer upstream Rich unless you specifically need this exact fork as a local snapshot. The fork adds no visible features and is materially behind upstream, so it is a weaker choice for adopters who want current fixes and active maintenance.

Choose this fork only if you explicitly want an old, frozen Rich baseline. For most adopters, upstream is the better choice because this fork adds nothing and is far behind current maintenance.

Choose upstream unless you specifically need this older snapshot; this fork adds no visible features and is materially behind upstream.