This page compares the source lines of code (SLOC) of BurntSushi/ripgrep and sharkdp/fd using cached OctoCounts reports. Code size is not code quality: a larger count only means more source material, not a better or worse project.
As of 2026-09-06, BurntSushi/ripgrep contains 46,567 total lines (35,349 code) across 128 files, while sharkdp/fd contains 6,753 total lines (4,210 code) across 35 files as of 2026-08-26. BurntSushi/ripgrep is about 8.4x the size of sharkdp/fd by code lines. Code size is not code quality: a larger count only means more source material, not a better or worse project.
| Metric | BurntSushi/ripgrep | sharkdp/fd |
|---|---|---|
| Files | 128 | 35 |
| Total lines | 46,567 | 6,753 |
| Code lines | 35,349 | 4,210 |
| Comment lines | 6,267 | 1,401 |
| Blank lines | 4,951 | 1,142 |
| Languages counted | 10 | 8 |
Top languages in BurntSushi/ripgrep: Rust (92.4% of code), Python (3.2% of code), YAML (1.8% of code). Top languages in sharkdp/fd: Rust (93.1% of code), Shell (2.8% of code), TOML (2.2% of code). Rust, TOML appear in both top language lists; Python, YAML, Zsh appear only in BurntSushi/ripgrep's top languages; Shell, Makefile, AWK appear only in sharkdp/fd's top languages.
Methodology: both counts come from cached OctoCounts reports generated with tokei. BurntSushi/ripgrep was counted at ref c1fc6a5eb8c971fc43041d3df34cf8bd49f31032 (commit c1fc6a5eb8c9) on 2026-09-06; sharkdp/fd was counted at ref master (commit fe0e455feea8) on 2026-08-26. See the counting methodology for ignored directories and analysis options.
Evidence and next steps:
Note: code size is not code quality. OctoCounts only reports reproducible line counts and makes no claim that either project is better.
BurntSushi/ripgrep has more code: 35,349 code lines versus 4,210 for sharkdp/fd, about 8.4x as much, based on cached OctoCounts reports as of 2026-09-06.
Not necessarily. SLOC measures size, not complexity, quality, or maintainability. A larger codebase can mean more features, more generated or vendored code, more verbose language idioms, or more tests — none of which imply the code is harder to work with. Use SLOC to gauge the scale of what you'd be reading or maintaining, not as a quality signal for BurntSushi/ripgrep, sharkdp/fd, or any repository.
Methodology: both counts come from cached OctoCounts reports generated with tokei. BurntSushi/ripgrep was counted at ref c1fc6a5eb8c971fc43041d3df34cf8bd49f31032 (commit c1fc6a5eb8c9) on 2026-09-06; sharkdp/fd was counted at ref master (commit fe0e455feea8) on 2026-08-26. See the counting methodology for ignored directories and analysis options.
Yes. This page shows the default branch for each repository. Use the interactive comparison tool to pick any public GitHub repository, branch, tag, or commit SHA for both sides and get a fresh side-by-side report.