# BurntSushi/ripgrep SLOC report

> As of 2026-09-06 (commit c1fc6a5eb8c9), BurntSushi/ripgrep contains 46,567 total lines: 35,349 code, 6,267 comments, 4,951 blank, across 128 files in 10 languages (top: Rust 92.4%). Custom configuration (tests excluded, docs excluded, generated excluded). Counted with tokei via OctoCounts.

BurntSushi/ripgrep has 35,349 source lines of code out of 46,567 total lines across 128 files, counted from the c1fc6a5eb8c971fc43041d3df34cf8bd49f31032 ref at commit c1fc6a5eb8c9 by the OctoCounts tokei engine on 2026-09-06. The report is cached by commit, tokei version, and analysis options, so recounting the same revision returns exactly these numbers.

OctoCounts produced this report by resolving BurntSushi/ripgrep to commit c1fc6a5eb8c9, downloading the repository source archive, and counting every source file with tokei, the open-source line counter written in Rust. The table below breaks the count down by programming language into files, total lines, code lines, comment lines, and blank lines, so the figures can be compared across languages and projects. Results are cached by commit, tokei version, and analysis options, so counting the same revision again reproduces exactly these numbers.

## Repository size insights

This is a medium-sized codebase by counted code lines. Code represents 75.9% of all lines, comments represent 13.5%, and the repository averages 276 code lines per file. Rust accounts for 92.4% of counted code.

| Language | Files | Lines | Code | Comments | Blanks |
| --- | ---: | ---: | ---: | ---: | ---: |
| Rust | 81 | 38,160 | 32,649 | 1,935 | 3,576 |
| Python | 2 | 1,346 | 1,143 | 45 | 158 |
| YAML | 5 | 747 | 626 | 66 | 55 |
| TOML | 12 | 441 | 371 | 23 | 47 |
| Zsh | 1 | 691 | 364 | 239 | 88 |
| Shell | 4 | 175 | 134 | 23 | 18 |
| Fish | 1 | 31 | 22 | 5 | 4 |
| XML | 1 | 28 | 21 | 7 | 0 |
| Ruby | 1 | 23 | 19 | 0 | 4 |
| Markdown | 20 | 4,925 | 0 | 3,924 | 1,001 |

Top language (Rust 92.4%). Generated at 2026-09-06T01:06:19.362217591+00:00. Canonical report: https://octocounts.com/github/BurntSushi/ripgrep

## Reproduce this report

[Reproduce this exact report and configuration](https://octocounts.com/github/BurntSushi/ripgrep/commit/c1fc6a5eb8c971fc43041d3df34cf8bd49f31032?analysis=%7B%22ignoredDirs%22%3A%5B%5D%2C%22ignoredLanguages%22%3A%5B%5D%2C%22profile%22%3A%22default%22%2C%22includeDocs%22%3Afalse%2C%22includeTests%22%3Afalse%2C%22includeGenerated%22%3Afalse%7D).

## Report FAQ

### How many lines of code does BurntSushi/ripgrep have?

BurntSushi/ripgrep has 46,567 total lines, including 35,349 code lines, 6,267 comment lines, and 4,951 blank lines.

### How was the BurntSushi/ripgrep line count measured?

OctoCounts resolved the public GitHub repository to commit c1fc6a5eb8c9, downloaded the source archive, counted it with tokei, and cached the report by commit, tokei version, and analysis options.

### What commit was counted for BurntSushi/ripgrep?

This OctoCounts report was generated from c1fc6a5eb8c971fc43041d3df34cf8bd49f31032 at commit c1fc6a5eb8c9 on 2026-09-06T01:06:19.362217591+00:00.

## Similar repository reports

- [rwf2/rocket](https://octocounts.com/github/rwf2/rocket) — Rust, 35,502 code lines
- [mlm-games/miniter](https://octocounts.com/github/mlm-games/miniter) — Rust, 35,110 code lines
- [RyanCodrai/turbovec](https://octocounts.com/github/RyanCodrai/turbovec) — Rust, 34,699 code lines
- [rokokol/MolvAI](https://octocounts.com/github/rokokol/MolvAI) — Rust, 36,052 code lines
- [leeguooooo/iphone-use](https://octocounts.com/github/leeguooooo/iphone-use) — Rust, 36,513 code lines
- [noh-rs/nohrs](https://octocounts.com/github/noh-rs/nohrs) — Rust, 37,099 code lines

## Related OctoCounts pages

- [Recently analyzed repositories](https://octocounts.com/recent)
- [Popular SLOC reports](https://octocounts.com/popular)
- [Trending GitHub repositories](https://octocounts.com/trending)
- [Hall of Monoliths](https://octocounts.com/hall-of-monoliths)
- [Rust vs Go](https://octocounts.com/compare/rust-vs-go)
- [Electron vs Tauri](https://octocounts.com/compare/electron-vs-tauri)
- [Deno vs Node.js](https://octocounts.com/compare/deno-vs-node)
- [GitHub SLOC counter guide](https://octocounts.com/docs/github-sloc-counter)
- [Counting methodology](https://octocounts.com/docs/methodology)
- [SLOC and code metrics glossary](https://octocounts.com/docs/glossary)
- [Original research: how filtering changes SLOC counts](https://octocounts.com/research)
- [OctoCounts API docs](https://octocounts.com/docs/api)