# Grafana vs Kibana: source lines of code compared

As of 2026-09-07, grafana/grafana contains 4,342,761 total lines (3,743,700 code) across 20,114 files, while elastic/kibana contains 12,905,552 total lines (10,491,473 code) across 102,021 files as of 2026-09-07. elastic/kibana is about 2.8x the size of grafana/grafana by code lines. Code size is not code quality: a larger count only means more source material, not a better or worse project.

| Metric | [grafana/grafana](https://octocounts.com/github/grafana/grafana) | [elastic/kibana](https://octocounts.com/github/elastic/kibana) |
| --- | ---: | ---: |
| Files | 20,114 | 102,021 |
| Total lines | 4,342,761 | 12,905,552 |
| Code lines | 3,743,700 | 10,491,473 |
| Comment lines | 229,836 | 1,190,933 |
| Blank lines | 369,225 | 1,223,146 |
| Languages counted | 12 | 12 |

Top languages in grafana/grafana: JSON (34.4% of code), Go (30.5% of code), TypeScript (16.3% of code). Top languages in elastic/kibana: TypeScript (56.8% of code), TSX (28.7% of code), JSON (7.2% of code). JSON, TypeScript, TSX appear in both top language lists; Go, SVG appear only in grafana/grafana's top languages; YAML, JavaScript appear only in elastic/kibana's top languages.

Methodology: both counts come from cached OctoCounts reports generated with tokei. grafana/grafana was counted at ref main (commit 8a768495e10c) on 2026-09-07; elastic/kibana was counted at ref main (commit 6f5c1c30b965) on 2026-09-07. See the [counting methodology](https://octocounts.com/docs/methodology) for ignored directories and analysis options.
Evidence and next steps:

- [grafana/grafana SLOC report](https://octocounts.com/github/grafana/grafana)
- [elastic/kibana SLOC report](https://octocounts.com/github/elastic/kibana)
- [Compare grafana/grafana and elastic/kibana interactively](https://octocounts.com/compare?left=https%3A%2F%2Fgithub.com%2Fgrafana%2Fgrafana&right=https%3A%2F%2Fgithub.com%2Felastic%2Fkibana)

Note: code size is not code quality. OctoCounts only reports reproducible line counts and makes no claim that either project is better.

## Compare FAQ

### Which has more lines of code, grafana/grafana or elastic/kibana?

elastic/kibana has more code: 10,491,473 code lines versus 3,743,700 for grafana/grafana, about 2.8x as much, based on cached OctoCounts reports as of 2026-09-07.

### Does more source lines of code mean more complexity?

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 grafana/grafana, elastic/kibana, or any repository.

### How is this comparison calculated?

Methodology: both counts come from cached OctoCounts reports generated with tokei. grafana/grafana was counted at ref main (commit 8a768495e10c) on 2026-09-07; elastic/kibana was counted at ref main (commit 6f5c1c30b965) on 2026-09-07. See the counting methodology for ignored directories and analysis options.

### Can I compare a different branch, tag, or commit?

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.

## Related OctoCounts pages

- [Interactive repository comparison](https://octocounts.com/compare)
- [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)
- [GitHub SLOC counter guide](https://octocounts.com/docs/github-sloc-counter)
- [Counting methodology](https://octocounts.com/docs/methodology)
- [OctoCounts API docs](https://octocounts.com/docs/api)