# SeongGino/Nero-umu SLOC report

> SeongGino/Nero-umu: 4,913 code lines at commit f7f6d2b33d79, counted with tokei-15.0.0 on 2026-11-01. Saved result a37144375b72d582b58faae7c898f2ff0b19326c60a7dbbc8fd3635dfe856151.

SeongGino/Nero-umu has 4,913 source lines of code out of 6,522 total lines across 32 files, counted with tokei from the main ref at commit f7f6d2b33d79 on November 1, 2026. Tests, docs and generated files are excluded under OctoCounts' canonical public options.

OctoCounts produced this report by resolving SeongGino/Nero-umu to commit f7f6d2b33d79, 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

SeongGino/Nero-umu: 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 small codebase by counted code lines. Code represents 75.3% of all lines, comments represent 12.3%, and the repository averages 154 code lines per file. C++ accounts for 78.8% of counted code.

| Language | Files | Lines | Code | Comments | Blanks |
| --- | ---: | ---: | ---: | ---: | ---: |
| C++ | 15 | 4,825 | 3,872 | 441 | 512 |
| C Header | 14 | 1,459 | 940 | 263 | 256 |
| CMake | 1 | 116 | 98 | 1 | 17 |
| TypeScript | 1 | 3 | 3 | 0 | 0 |
| Markdown | 1 | 119 | 0 | 95 | 24 |

Top language: C++ 78.8%. Generated on November 1, 2026. Canonical report: https://octocounts.com/github/SeongGino/Nero-umu/commit/f7f6d2b33d79f66deb942e6acfb1a225bdbc2ef8?reportId=a37144375b72d582b58faae7c898f2ff0b19326c60a7dbbc8fd3635dfe856151&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/SeongGino/Nero-umu/commit/f7f6d2b33d79f66deb942e6acfb1a225bdbc2ef8?reportId=a37144375b72d582b58faae7c898f2ff0b19326c60a7dbbc8fd3635dfe856151&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 SeongGino/Nero-umu have?

SeongGino/Nero-umu has 4,913 lines of code, plus 800 comment lines and 809 blank lines, for 6,522 total lines at commit f7f6d2b33d79 on November 1, 2026. Tests, docs and generated files are excluded under OctoCounts' canonical public options.

### How was the SeongGino/Nero-umu line count measured?

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

### What commit was counted for SeongGino/Nero-umu?

This OctoCounts report was generated from main at commit f7f6d2b33d79 on November 1, 2026.

## 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)
