GoogleChromeLabs/chrome-for-testing

GoogleChromeLabs/chrome-for-testing has 351,708 source lines of code out of 352,187 total lines across 24 files, counted with tokei from the main ref at commit 7106ed849769 on November 16, 2026. Tests, docs and generated files are excluded under OctoCounts' canonical public options.

GoogleChromeLabs/chrome-for-testing: 351,708 code lines at commit 7106ed849769, counted with tokei-15.0.0 on 2026-11-16. Saved result 767432f584333a4a2d461354749daf918a78ab1101f30b82ced76e6b04f39f59.

OctoCounts produced this report by resolving GoogleChromeLabs/chrome-for-testing to commit 7106ed849769, 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.

Repository size insights

This is a large codebase by counted code lines. Code represents 99.9% of all lines, comments represent 0.1%, and the repository averages 14,655 code lines per file. JavaScript is the largest programming language at 0.2% of counted code; data and prose formats such as JSON or YAML hold a larger share.

LanguageFilesLinesCodeCommentsBlanks
JSON1035097935097900
JavaScript1098071318285
HTML13015150
SVG11100
Markdown2197014849

Top programming language: JavaScript 0.2%. Generated on .

Counting rules and retention

GoogleChromeLabs/chrome-for-testing: 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.

Reproduce this report

Reproduce this exact report and configuration.

Report FAQ

How many lines of code does GoogleChromeLabs/chrome-for-testing have?

GoogleChromeLabs/chrome-for-testing has 351,708 lines of code, plus 345 comment lines and 134 blank lines, for 352,187 total lines at commit 7106ed849769 on November 16, 2026. Tests, docs and generated files are excluded under OctoCounts' canonical public options.

How was the GoogleChromeLabs/chrome-for-testing line count measured?

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

What commit was counted for GoogleChromeLabs/chrome-for-testing?

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

Similar repository reports

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

Play the growth animation for GoogleChromeLabs/chrome-for-testing on this page — 351,708 code lines across 5 languages, counted by tokei.