# leegarchat/twrp_device_google_pixels SLOC report

> leegarchat/twrp_device_google_pixels: 131,885 code lines at commit 5f52f89eeaf8, counted with tokei-15.0.0 on 2026-11-15. Saved result 9327097c22577fa05e84d22ce32efda7f1b68531ff8d5f9cf9a469d38926c80d.

leegarchat/twrp_device_google_pixels has 131,885 source lines of code out of 230,330 total lines across 360 files, counted with tokei from the R12_16 ref at commit 5f52f89eeaf8 on November 15, 2026. Tests, docs and generated files are excluded under OctoCounts' canonical public options.

OctoCounts produced this report by resolving leegarchat/twrp_device_google_pixels to commit 5f52f89eeaf8, downloading the repository source archive, and counting files selected by the effective rules 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; an exact reproduction needs the same commit, engine version, and effective counting rules.

## Counting rules and retention

leegarchat/twrp_device_google_pixels: tokei-15.0.0, policy directories-v1; docs excluded, tests excluded, generated excluded. Excluded directory names: .cache, .generated, .git, .next, __tests__, build, dist, doc, docs, documentation, fixtures, gen, generated, node_modules, target, test, tests, vendor. Ignored languages: none. Repository declarations: off. Exclusions are rule-based; they do not prove that every test, document or generated file was removed.

Saved reports remain subject to cache cleanup and replacement. Export the JSON or text for durable citation; live repository URLs can change.

## Repository size insights

This is a large codebase by counted code lines. Code represents 57.3% of all lines, comments represent 30.5%, and the repository averages 366 code lines per file. C++ accounts for 55.3% of counted code.

| Language | Files | Lines | Code | Comments | Blanks |
| --- | ---: | ---: | ---: | ---: | ---: |
| C++ | 87 | 90,303 | 72,887 | 7,726 | 9,690 |
| Rust | 73 | 20,030 | 17,596 | 1,225 | 1,209 |
| C | 25 | 14,185 | 10,761 | 1,711 | 1,713 |
| XML | 22 | 12,161 | 10,393 | 477 | 1,291 |
| Python | 10 | 5,240 | 4,442 | 224 | 574 |
| JSON | 35 | 4,216 | 4,106 | 0 | 110 |
| Shell | 18 | 5,876 | 4,089 | 1,391 | 396 |
| C++ Header | 4 | 4,388 | 3,232 | 559 | 597 |
| C Header | 39 | 5,133 | 2,953 | 1,186 | 994 |
| Go | 4 | 801 | 672 | 46 | 83 |
| Makefile | 10 | 483 | 262 | 151 | 70 |
| Batch | 1 | 241 | 230 | 0 | 11 |
| TOML | 8 | 189 | 157 | 7 | 25 |
| Bazel | 5 | 130 | 105 | 15 | 10 |
| Markdown | 5 | 702 | 0 | 556 | 146 |
| Plain Text | 14 | 66,252 | 0 | 55,073 | 11,179 |

Top language: C++ 55.3%. Generated on November 15, 2026. Canonical report: https://octocounts.com/github/leegarchat/twrp_device_google_pixels/commit/5f52f89eeaf8ee34b2e828c198e5c7d866e0fe85?reportId=9327097c22577fa05e84d22ce32efda7f1b68531ff8d5f9cf9a469d38926c80d&analysis=%7B%22profile%22%3A%22default%22%2C%22ignoredDirs%22%3A%5B%5D%2C%22includeDocs%22%3Afalse%2C%22includeTests%22%3Afalse%2C%22ignoredLanguages%22%3A%5B%5D%2C%22includeGenerated%22%3Afalse%7D

## Reproduce this report

[Reproduce this exact report and configuration](https://octocounts.com/github/leegarchat/twrp_device_google_pixels/commit/5f52f89eeaf8ee34b2e828c198e5c7d866e0fe85?reportId=9327097c22577fa05e84d22ce32efda7f1b68531ff8d5f9cf9a469d38926c80d&analysis=%7B%22profile%22%3A%22default%22%2C%22ignoredDirs%22%3A%5B%5D%2C%22includeDocs%22%3Afalse%2C%22includeTests%22%3Afalse%2C%22ignoredLanguages%22%3A%5B%5D%2C%22includeGenerated%22%3Afalse%7D).

## Report FAQ

### How many lines of code does leegarchat/twrp_device_google_pixels have?

leegarchat/twrp_device_google_pixels has 131,885 lines of code, plus 70,347 comment lines and 28,098 blank lines, for 230,330 total lines at commit 5f52f89eeaf8 on November 15, 2026. Tests, docs and generated files are excluded under OctoCounts' canonical public options.

### How was the leegarchat/twrp_device_google_pixels line count measured?

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

### What commit was counted for leegarchat/twrp_device_google_pixels?

This OctoCounts report was generated from R12_16 at commit 5f52f89eeaf8 on November 15, 2026.

## Similar repository reports

- [CHMOSE023/LearnMiniCAD](https://octocounts.com/github/CHMOSE023/LearnMiniCAD) — C++, 132,870 code lines
- [hyprwm/Hyprland](https://octocounts.com/github/hyprwm/Hyprland) — C++, 129,239 code lines
- [microsoft/WSL](https://octocounts.com/github/microsoft/WSL) — C++, 134,700 code lines
- [devscafecommunity/caffeine](https://octocounts.com/github/devscafecommunity/caffeine) — C++, 140,782 code lines
- [vs-sr-dev/n64-lba2](https://octocounts.com/github/vs-sr-dev/n64-lba2) — C++, 140,960 code lines
- [argotorg/solidity](https://octocounts.com/github/argotorg/solidity) — C++, 123,192 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)
- [TensorFlow vs PyTorch](https://octocounts.com/compare/tensorflow-vs-pytorch)
- [Electron vs Tauri](https://octocounts.com/compare/electron-vs-tauri)
- [Godot vs Bevy](https://octocounts.com/compare/godot-vs-bevy)
- [How to count lines of code in a GitHub repository](https://octocounts.com/docs/count-lines-of-code-github)
- [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)
- [All OctoCounts guides](https://octocounts.com/docs)
