sharkdp/bat

Prefer upstream unless you specifically need this fork as a private baseline; it is materially behind and adds no visible capabilities.

Prefer upstream unless you specifically need this fork's custom syntax/asset behavior and are willing to own an outdated codebase. For most adopters, the fork is too stale and too far behind to be a safe default.

Prefer this fork only if its feature-gated, library-friendly direction is specifically what you need and you are prepared to maintain a large upstream gap. For most adopters, upstream `sharkdp/bat` is the safer choice because this fork is stale and heavily diverged.

Prefer upstream unless you need one of the fork-specific legacy options like `BAT_OPTS` or `--no-config`. This fork is far behind and looks suitable only as a historical customization base, not as a current drop-in replacement.

Prefer upstream unless you specifically need a frozen older baseline. This fork adds no evident capabilities and is far behind current upstream maintenance.

Choose this fork only if its specific customizations are already the target behavior. For most users, upstream sharkdp/bat is the safer choice because this fork is stale, substantially behind, and likely missing many newer fixes and features.

Prefer upstream unless you specifically need this fork's custom syntax/rendering changes; the fork is materially stale and highly divergent, so it is a maintenance choice rather than a general-purpose replacement.

Choose this fork if you want bat as a living derivative with extra terminal ergonomics and control-character handling. Choose upstream if you need maximum compatibility and minimal divergence.