gnutools/glibc

gnutools/glibc has 1,699,032 source lines of code out of 2,482,203 total lines across 17,996 files, counted from the master ref at commit fea6c3582ae1 by the OctoCounts tokei engine on 2026-10-24. The report is cached by commit, tokei version, and analysis options, reproduction requires the same commit, engine version, and effective counting rules. Unknown rules in older reports prevent exact reproduction.

gnutools/glibc: 1,699,032 code lines at commit fea6c3582ae1, counted with tokei-14.0.0 on 2026-10-24. Saved result 4806bc6a4dc9d69c83bb767108589e9c1589a3d396cb1579207122de55914660.

OctoCounts produced this report by resolving gnutools/glibc to commit fea6c3582ae1, 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, exact reproduction requires the same commit, engine version, and effective counting rules. Older reports with unknown rules cannot promise exact reproduction.

Counting rules and retention

gnutools/glibc: tokei-14.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.

Reproduce this report

Reproduce this exact report and configuration.

Report FAQ

How many lines of code does gnutools/glibc have?

gnutools/glibc has 2,482,203 total lines, including 1,699,032 code lines, 553,027 comment lines, and 230,144 blank lines.

How was the gnutools/glibc line count measured?

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

What commit was counted for gnutools/glibc?

This OctoCounts report was generated from master at commit fea6c3582ae1 on 2026-10-24T12:06:04.573656039Z.

Similar repository reports

Other public repositories with an OctoCounts report, ranked by top language and code size similarity:

• python/cpython — C, 1,646,068 code lines
• postgres/postgres — C, 1,632,495 code lines
• php/php-src — C, 1,802,285 code lines
• FFmpeg/FFmpeg — C, 1,588,230 code lines
• xeonliu/FFmpeg-AVSPlus — C, 1,504,588 code lines
• tsirysndr/rockboxd — C, 2,063,553 code lines