Discofork
Repository brief

sharkdp/fd

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:01:35.964Z
1mo ago

sharkdp/fd

`sharkdp/fd` is a mature Rust command-line filesystem search tool positioned as a simple, fast, user-friendly alternative to `find`. It is actively maintained, widely used, and has a large fork/stars footprint, which can make its forks interesting for feature extensions, packaging changes, and platform-specific adaptations rather than basic maintenance.

GitHub
Loading tags...
Stars42,245
Forks1,022
Default branchmaster
Last pushed2026-03-28T16:30:12Z
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

Prefer upstream unless you specifically need this exact older snapshot; this fork offers no visible functional upside and appears to lag upstream by 24 commits.

Prefer this fork only if you need its Git-ignore override or downstream packaging tweaks. For most users, upstream `sharkdp/fd` is the safer choice because this fork appears heavily diverged and likely behind on ongoing maintenance.

Adopt this only if you specifically want a mostly unmodified snapshot of fd; otherwise upstream is the better choice because this fork adds nothing and is slightly behind.

Choose this fork if your priority is a leaner, easier-to-package `fd`. Choose upstream if you want the latest fixes and the broadest supported build/features with minimal divergence.

Prefer upstream `sharkdp/fd` unless you need this exact fork as a starting point; it adds no visible capabilities and is behind by 37 commits.

Choose this fork only if you specifically want an old snapshot of `fd`; otherwise upstream is the better default because this fork adds nothing visible and is 40 commits behind.

Choose this fork only if `--exec-print-separator` solves a real workflow pain point. Otherwise, upstream `fd` is the better default because this fork is materially behind and adds only a narrow execution-output feature.

Choose this fork only if the license consolidation is the main reason you need it. For most users, upstream `fd` is the safer choice because it is actively maintained and this fork does not add meaningful functional capabilities.

Prefer upstream unless you specifically need this fork as a workspace for your own changes. This fork currently adds no visible value and mainly carries the risk of being out of date.

Choose upstream instead unless you specifically need this exact frozen snapshot; the fork adds no visible capabilities and is far behind current fd.