Repository brief

dandavison/delta

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-30T20:00:31.732Z
1mo ago

dandavison/delta

`dandavison/delta` is a Rust command-line pager for git, diff, grep, and blame output, focused on syntax highlighting and improved diff readability. It is active, not archived, and appears well maintained with very recent commits and releases.

GitHub
Loading tags...
Stars29,796
Forks483
Default branchmain
Last pushed2026-03-28T20:15:33Z
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

9 of 9 fork briefs
Selected

Prefer upstream unless you explicitly want this fork's older paging/CLI behavior or packaging tweaks. The fork is materially behind and looks best only for adopters who value a frozen, minimal variant over current features and maintenance.

Prefer upstream unless you specifically need this exact fork as a frozen baseline. It adds no visible features and is behind on recent upstream changes, so its main appeal is minimal divergence rather than capability.

Prefer upstream unless you specifically need this older snapshot. The fork adds no visible capabilities and is far behind current upstream maintenance.

Choose the fork if you want a conservative downstream variant with targeted fixes and workflow maintenance. Prefer upstream if you want the freshest feature work, docs, and release automation around delta's mainline experience.

Prefer upstream unless you specifically need this fork namespace. It offers no visible functional advantage, and it is already behind by 7 commits.

Prefer upstream `dandavison/delta` unless you specifically need this fork’s older snapshot or plan to do your own downstream work. This fork does not add user-facing capabilities and is behind recent upstream fixes.

Prefer upstream unless you specifically need this exact older snapshot. This fork adds no visible functionality and mainly represents lag behind an actively maintained project.

Prefer upstream unless you specifically need this fork's ownership or mirroring setup; it offers no visible extra functionality and is behind recent upstream work.

Choose upstream unless you specifically need this exact snapshot; the fork adds no visible capability and is materially behind current delta.