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 from the master ref at commit 5f1380bfdc3a by the OctoCounts tokei engine on 2026-09-21. The report is cached by commit, tokei version, and analysis options, so recounting the same revision returns exactly these numbers.

As of 2026-09-21 (commit 5f1380bfdc3a), PixelsCommander/fps-control-chrome-extension contains 441 total lines: 366 code, 30 comments, 45 blank, across 17 files in 5 languages (top: JavaScript 74.9%). Custom configuration (tests excluded, docs excluded, generated 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 every source file 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, so counting the same revision again reproduces exactly these numbers.

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 441 total lines, including 366 code lines, 30 comment lines, and 45 blank lines.

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 master at commit 5f1380bfdc3a on 2026-09-21T07:05:38.705838255+00:00.