# parse-community/parse-server SLOC report

> As of 2026-11-14 (commit 94bb96b2797a), parse-community/parse-server contains 242,123 total lines: 207,363 code, 15,911 comments, 18,849 blank, across 444 files in 9 languages (top language: JavaScript 77.1%). Canonical public options (tests, docs and generated files excluded). Counted with tokei via OctoCounts.

parse-community/parse-server has 207,363 source lines of code out of 242,123 total lines across 444 files, counted with tokei from the alpha ref at commit 94bb96b2797a on November 14, 2026. Tests, docs and generated files are excluded under OctoCounts' canonical public options.

OctoCounts produced this report by resolving parse-community/parse-server to commit 94bb96b2797a, 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

parse-community/parse-server: 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 large codebase by counted code lines. Code represents 85.6% of all lines, comments represent 6.6%, and the repository averages 467 code lines per file. JavaScript accounts for 77.1% of counted code.

| Language | Files | Lines | Code | Comments | Blanks |
| --- | ---: | ---: | ---: | ---: | ---: |
| JavaScript | 364 | 184,164 | 159,912 | 9,455 | 14,797 |
| JSON | 16 | 44,446 | 44,445 | 0 | 1 |
| TypeScript | 12 | 2,726 | 2,295 | 286 | 145 |
| HTML | 26 | 590 | 346 | 160 | 84 |
| Shell | 5 | 313 | 236 | 20 | 57 |
| SQL | 7 | 91 | 89 | 1 | 1 |
| Dockerfile | 1 | 77 | 40 | 23 | 14 |
| Markdown | 12 | 9,711 | 0 | 5,963 | 3,748 |
| Plain Text | 1 | 5 | 0 | 3 | 2 |

Top language: JavaScript 77.1%. Generated on November 14, 2026. Canonical report: https://octocounts.com/github/parse-community/parse-server

## Reproduce this report

[Reproduce this exact report and configuration](https://octocounts.com/github/parse-community/parse-server/commit/94bb96b2797a0104da787d6db06193f719ab1397?analysis=%7B%22ignoredDirs%22%3A%5B%5D%2C%22ignoredLanguages%22%3A%5B%5D%2C%22profile%22%3A%22default%22%2C%22includeDocs%22%3Afalse%2C%22includeTests%22%3Afalse%2C%22includeGenerated%22%3Afalse%7D&reportId=9ac1983e3f2c2a936f051a10c159011872ea65e93f5d410f95d8237caff0690b).

## Report FAQ

### How many lines of code does parse-community/parse-server have?

parse-community/parse-server has 207,363 lines of code, plus 15,911 comment lines and 18,849 blank lines, for 242,123 total lines at commit 94bb96b2797a on November 14, 2026. Tests, docs and generated files are excluded under OctoCounts' canonical public options.

### How was the parse-community/parse-server line count measured?

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

### What commit was counted for parse-community/parse-server?

This OctoCounts report was generated from alpha at commit 94bb96b2797a on November 14, 2026.

## Similar repository reports

- [career-ops-hq/career-ops](https://octocounts.com/github/career-ops-hq/career-ops) — JavaScript, 209,506 code lines
- [Javis603/token-monitor](https://octocounts.com/github/Javis603/token-monitor) — JavaScript, 211,077 code lines
- [ancsemi/Haven](https://octocounts.com/github/ancsemi/Haven) — JavaScript, 212,634 code lines
- [201206030/novel-plus](https://octocounts.com/github/201206030/novel-plus) — JavaScript, 214,451 code lines
- [SillyTavern/SillyTavern](https://octocounts.com/github/SillyTavern/SillyTavern) — JavaScript, 214,571 code lines
- [Smithjean330/little-infer](https://octocounts.com/github/Smithjean330/little-infer) — JavaScript, 217,252 code lines

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