PixelsCommander/fps-control-chrome-extension

PixelsCommander/fps-control-chrome-extension has 366 source lines of code out of 441 total lines across 17 files, counted with tokei from the 5f1380bfdc3a59408ef364daf15281cf261478e2 ref at commit 5f1380bfdc3a on November 9, 2026. Tests, docs and generated files are excluded under OctoCounts' canonical public options.

As of 2026-11-09 (commit 5f1380bfdc3a), PixelsCommander/fps-control-chrome-extension contains 441 total lines: 366 code, 30 comments, 45 blank, across 17 files in 5 languages (top language: JavaScript 74.9%). Canonical public options (tests, docs and generated files excluded). Counted with tokei via OctoCounts.

As of 2026-11-09 (commit 5f1380bfdc3a), PixelsCommander/fps-control-chrome-extension contains 441 total lines: 366 code, 30 comments, 45 blank, across 17 files in 5 languages (top language: JavaScript 74.9%). Canonical public options (tests, docs and generated files excluded). Counted with tokei via OctoCounts.

OctoCounts produced this report by resolving PixelsCommander/fps-control-chrome-extension to commit 5f1380bfdc3a, 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 small codebase by counted code lines. Code represents 83.0% of all lines, comments represent 6.8%, and the repository averages 22 code lines per file. JavaScript accounts for 74.9% of counted code.

LanguageFilesLinesCodeCommentsBlanks
JavaScript8314274535
HTML3484602
JSON2464600
CSS20000
Markdown2330258

Top language: JavaScript 74.9%. Generated on .

Counting rules and retention

PixelsCommander/fps-control-chrome-extension: 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 PixelsCommander/fps-control-chrome-extension have?

PixelsCommander/fps-control-chrome-extension has 366 lines of code, plus 30 comment lines and 45 blank lines, for 441 total lines at commit 5f1380bfdc3a on November 9, 2026. Tests, docs and generated files are excluded under OctoCounts' canonical public options.

How was the PixelsCommander/fps-control-chrome-extension line count measured?

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

What commit was counted for PixelsCommander/fps-control-chrome-extension?

This OctoCounts report was generated from 5f1380bfdc3a59408ef364daf15281cf261478e2 at commit 5f1380bfdc3a on November 9, 2026.

Play the growth animation for PixelsCommander/fps-control-chrome-extension on this page — 366 code lines across 5 languages, counted by tokei.