sharkdp/fd

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.