# PixelsCommander/fps-control-chrome-extension SLOC report

> PixelsCommander/fps-control-chrome-extension: 366 code lines at commit 5f1380bfdc3a, counted with tokei-15.0.0 on 2026-11-09. Saved result 803c3fcb69d69d1fb56ffbc90a6441dd9bb6f39e83aa53d6caed5673a7052e56.

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.

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.

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

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

| Language | Files | Lines | Code | Comments | Blanks |
| --- | ---: | ---: | ---: | ---: | ---: |
| JavaScript | 8 | 314 | 274 | 5 | 35 |
| HTML | 3 | 48 | 46 | 0 | 2 |
| JSON | 2 | 46 | 46 | 0 | 0 |
| CSS | 2 | 0 | 0 | 0 | 0 |
| Markdown | 2 | 33 | 0 | 25 | 8 |

Top language: JavaScript 74.9%. Generated on November 9, 2026. Canonical report: https://octocounts.com/github/PixelsCommander/fps-control-chrome-extension/commit/5f1380bfdc3a59408ef364daf15281cf261478e2?reportId=803c3fcb69d69d1fb56ffbc90a6441dd9bb6f39e83aa53d6caed5673a7052e56&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/PixelsCommander/fps-control-chrome-extension/commit/5f1380bfdc3a59408ef364daf15281cf261478e2?reportId=803c3fcb69d69d1fb56ffbc90a6441dd9bb6f39e83aa53d6caed5673a7052e56&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 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.

## 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)
- [React vs Vue](https://octocounts.com/compare/react-vs-vue)
- [Next.js vs Vite](https://octocounts.com/compare/nextjs-vs-vite)
- [Vite vs webpack](https://octocounts.com/compare/vite-vs-webpack)
- [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)
