/jump to repo

Repos Recent Bookmarks Watched Notes Tags Discover Compare Stats GitHub

Repository brief

BurntSushi/ripgrep

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-30T13:01:21.832Z

3mo ago

BurntSushi/ripgrep

ripgrep is a Rust command-line search tool for recursively finding regex matches while respecting `.gitignore`, hidden files, and binary files by default. It is a mature, actively maintained project with very high adoption: 61,583 stars, 2,450 forks, and a recent push on 2026-02-27.

Loading tags...

Stars61,583

Forks2,450

Default branchmaster

Last pushed2026-02-27T16:25:19Z

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

Maintenance:

Magnitude:

Sort:

Selected

Prefer upstream unless you specifically need this fork's older architecture or a fork-only workflow. The fork looks significantly diverged and stale, with meaningful removals and a high maintenance burden.

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.

Fork comparison

sharkdp/ripgrep

38/100

stale

significant_divergence

Prefer upstream unless you specifically need this fork's older architecture or a fork-only workflow. The fork looks significantly diverged and stale, with meaningful removals and a high maintenance burden.

Likely purpose

A heavily diverged older ripgrep line that looks like a maintained-at-one-point derivative rather than a current upstream-tracking fork, with broad refactors and removals around CLI structure, printing, ignore walking, and tests.

Best for

Users intentionally staying on this fork for a specific legacy behavior or packaging setup.; Maintainers who want to study or preserve an older ripgrep architecture.; People who can tolerate divergence and do not need the latest upstream feature set or fixes.

Additional features

A reorganized command-line/app structure centered around `src/app.rs` and `src/args.rs` rather than upstream's current layout.
A split-out printing crate path (`grep-printer`) and related refactoring, suggesting a more modular internal architecture.
Changes to ignore-walking and file-type handling, including a new `container` type covering both `Dockerfile` and `Containerfile`.
Build, packaging, and benchmark/test harness adjustments across CI, Debian/Homebrew, and benchsuite workflows.
Changes agent workflow behavior, such as prompt handling, handoffs, worktrees, memory, or orchestration flow.

Missing features

Materially behind upstream by roughly 200 commits each way, so it likely lacks many newer fixes, docs, and small feature updates from upstream.
Hyperlink output support appears to have been removed or made less available because `crates/printer/src/hyperlink/mod.rs` was deleted.
Some upstream-regression coverage and edge-case test data were removed or shrunk, including large NUL-containing fixtures and regression tests.
Current upstream module layout and APIs are no longer a drop-in match, making this fork harder to adopt as a straight replacement.
It trails upstream by 200 commits, so some recent upstream features and fixes are likely not present yet.

Strengths

May appeal to users who want the fork's older, more centralized app/CLI shape.
Useful if you need the fork's specific ignore/type handling and packaging adjustments.
Could be attractive to maintainers looking for a historical branch with substantial internal refactoring already done.

Risks

Staleness is the biggest risk: pushed in 2020 and far from upstream evolution.
Large deletions in core flags, printer, hyperlink, and tests suggest behavioral drift and possible regressions.
High divergence makes rebasing or cherry-picking upstream fixes expensive.
Adoption risk is high if you depend on current ripgrep flags, output behavior, or test coverage.

BurntSushi/ripgrep · Discofork