# jaegertracing/jaeger SLOC report

> jaegertracing/jaeger: 222,645 code lines at commit ffdd7d3c30d5, counted with tokei-15.0.0 on 2026-11-16. Saved result b0299a572699c3f56c6dd14f1b5e0deccfbd461f4821d318caf4d484123d7f96.

jaegertracing/jaeger has 222,645 source lines of code out of 280,152 total lines across 1,835 files, counted with tokei from the main ref at commit ffdd7d3c30d5 on November 16, 2026. Tests, docs and generated files are excluded under OctoCounts' canonical public options.

OctoCounts produced this report by resolving jaegertracing/jaeger to commit ffdd7d3c30d5, 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

jaegertracing/jaeger: 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 79.5% of all lines, comments represent 10.4%, and the repository averages 121 code lines per file. Go accounts for 81.7% of counted code.

| Language | Files | Lines | Code | Comments | Blanks |
| --- | ---: | ---: | ---: | ---: | ---: |
| Go | 1,287 | 224,115 | 181,895 | 19,324 | 22,896 |
| JSON | 182 | 20,454 | 20,448 | 0 | 6 |
| Shell | 53 | 8,343 | 6,541 | 695 | 1,107 |
| Python | 46 | 7,185 | 5,661 | 461 | 1,063 |
| YAML | 88 | 4,699 | 3,673 | 609 | 417 |
| SQL | 67 | 2,166 | 2,101 | 65 | 0 |
| Templ | 6 | 1,085 | 996 | 6 | 83 |
| Makefile | 11 | 1,247 | 850 | 217 | 180 |
| Protocol Buffers | 4 | 383 | 155 | 158 | 70 |
| HTML | 3 | 171 | 150 | 8 | 13 |
| Dockerfile | 8 | 200 | 108 | 40 | 52 |
| TOML | 2 | 74 | 42 | 22 | 10 |
| JavaScript | 3 | 34 | 25 | 6 | 3 |
| Markdown | 70 | 9,984 | 0 | 7,377 | 2,607 |
| Plain Text | 5 | 12 | 0 | 10 | 2 |

Top language: Go 81.7%. Generated on November 16, 2026. Canonical report: https://octocounts.com/github/jaegertracing/jaeger/commit/ffdd7d3c30d5719323af90a4e027c15bbea2682e?reportId=b0299a572699c3f56c6dd14f1b5e0deccfbd461f4821d318caf4d484123d7f96&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/jaegertracing/jaeger/commit/ffdd7d3c30d5719323af90a4e027c15bbea2682e?reportId=b0299a572699c3f56c6dd14f1b5e0deccfbd461f4821d318caf4d484123d7f96&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 jaegertracing/jaeger have?

jaegertracing/jaeger has 222,645 lines of code, plus 28,998 comment lines and 28,509 blank lines, for 280,152 total lines at commit ffdd7d3c30d5 on November 16, 2026. Tests, docs and generated files are excluded under OctoCounts' canonical public options.

### How was the jaegertracing/jaeger line count measured?

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

### What commit was counted for jaegertracing/jaeger?

This OctoCounts report was generated from main at commit ffdd7d3c30d5 on November 16, 2026.

## Similar repository reports

- [Lychee-Technology/forma](https://octocounts.com/github/Lychee-Technology/forma) — Go, 221,131 code lines
- [kubernetes-sigs/agent-sandbox](https://octocounts.com/github/kubernetes-sigs/agent-sandbox) — Go, 219,780 code lines
- [rocket-pool/smartnode](https://octocounts.com/github/rocket-pool/smartnode) — Go, 227,958 code lines
- [pathbox/learning-go](https://octocounts.com/github/pathbox/learning-go) — Go, 216,813 code lines
- [xoai/sage-wiki](https://octocounts.com/github/xoai/sage-wiki) — Go, 229,100 code lines
- [plimsollmark/plimsoll](https://octocounts.com/github/plimsollmark/plimsoll) — Go, 216,261 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)
- [Deno vs Node.js](https://octocounts.com/compare/deno-vs-node)
- [Kubernetes vs Terraform](https://octocounts.com/compare/kubernetes-vs-terraform)
- [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)
