BurntSushi/ripgrep

Choose this fork only if you need its Cosmopolitan-oriented platform/workflow changes. If you just want ripgrep, upstream is the safer default because this fork is substantially behind and likely incompatible in small but important ways.

Prefer upstream unless you specifically need this fork's custom architecture or legacy behavior. Adopt this fork only if you are prepared to own a stale, highly divergent codebase and do not need current ripgrep fixes or compatibility.

Prefer upstream unless you specifically need this older, unchanged snapshot. The fork adds no visible functionality and is far enough behind that adopters should expect missing fixes and docs from recent upstream work.

Prefer upstream unless you specifically need a dormant snapshot. This fork adds no visible features and is materially behind current upstream, so it is a poor choice for adopters who want ongoing fixes or enhancements.

Prefer this fork only if its custom workflow changes are specifically useful to you; otherwise upstream ripgrep is the safer default because it is far newer and actively maintained.

Choose this fork only if you specifically need its custom search and file-type behavior and can tolerate a long-stale codebase. For most users, upstream ripgrep is the safer default because this fork is materially outdated and heavily diverged.

Choose this fork only if its added config/CLI behavior is the reason you need it; otherwise upstream ripgrep is the safer default because this fork is very old and materially behind.

Prefer upstream ripgrep unless you specifically need this fork’s legacy/custom behavior or are prepared to maintain a long-stale, highly diverged codebase yourself.

Prefer this fork if your goal is to study, benchmark, or tune ripgrep performance on ARM/Apple Silicon. Stick with upstream if you just want the stable, mainstream CLI search tool, because this fork looks like a performance lab rather than a broadly differentiated product.