Discofork
Repository brief

junegunn/fzf

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:47:31.888Z
3mo ago

junegunn/fzf

`junegunn/fzf` is a very popular, actively maintained command-line fuzzy finder. It is a portable single-binary tool for interactive filtering of lists such as files, history, processes, hostnames, bookmarks, and git commits, with shell and editor integrations included.

GitHub
Loading tags...
Stars79,096
Forks2,743
Default branchmaster
Last pushed2026-03-30T04:20:11Z
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 its command-completion and binding behavior is the goal. For general-purpose adoption, upstream fzf is the safer choice because this fork is stale, heavily diverged, and likely missing years of fixes and platform support.

Choose this fork only if you specifically need the legacy MinGW-w64/Windows adaptation and can tolerate being years behind upstream. For most adopters, upstream fzf is the better choice because this fork is stale, heavily diverged, and missing many later fixes and integrations.

Choose this fork only if you need its specific terminal and shell behavior changes. If you just want fzf itself, upstream is the safer default because this fork is stale and substantially diverged.

Choose this fork only if you need its older, customized behavior and can live without upstream progress. For most users, upstream is the safer default because this fork is stale and materially behind.

Choose upstream unless you specifically need this fork’s historical behavior; this fork is too old and too divergent for most adopters, but it may still fit a legacy environment that depends on its custom terminal and option handling.

Choose this fork if abbreviation matching is the main product requirement and you can accept divergence from upstream. Prefer upstream fzf if you want the broadest compatibility, newest fixes, and the least maintenance risk.

Prefer this fork only if its UI, ANSI, or shell-integration changes match a specific workflow you need. If you want a broadly supported, current fzf with the latest fixes and the least adoption risk, upstream is the safer choice.

Choose upstream unless you specifically need this fork's older interaction tweaks or are maintaining an existing legacy deployment. For most adopters, the stale maintenance state and major divergence make the fork a poor default.

Choose this fork only if its specific defaults and shortcuts match your workflow closely enough to outweigh the maintenance risk. For most users, upstream is the safer choice; this fork suits people who value convenience tweaks over freshness and long-term compatibility.

Adopt this fork only if you need its older, specific behavior changes and are willing to own the maintenance burden. For most users, upstream is the better choice because this fork is stale and substantially behind.