This page compares the source lines of code (SLOC) of jestjs/jest and vitest-dev/vitest using cached OctoCounts reports. Code size is not code quality: a larger count only means more source material, not a better or worse project.
As of 2026-08-26, jestjs/jest contains 140,017 total lines (72,097 code) across 1,645 files, while vitest-dev/vitest contains 119,464 total lines (92,741 code) across 746 files as of 2026-08-26. vitest-dev/vitest is about 1.3x the size of jestjs/jest by code lines. Code size is not code quality: a larger count only means more source material, not a better or worse project.
| Metric | jestjs/jest | vitest-dev/vitest |
|---|---|---|
| Files | 1,645 | 746 |
| Total lines | 140,017 | 119,464 |
| Code lines | 72,097 | 92,741 |
| Comment lines | 43,834 | 14,645 |
| Blank lines | 24,086 | 12,078 |
| Languages counted | 12 | 11 |
Top languages in jestjs/jest: TypeScript (78.0% of code), JavaScript (11.2% of code), JSON (9.1% of code). Top languages in vitest-dev/vitest: TypeScript (75.3% of code), YAML (19.9% of code), JSON (1.9% of code). TypeScript, JavaScript, JSON appear in both top language lists; CSS, SVG appear only in jestjs/jest's top languages; YAML, Vue appear only in vitest-dev/vitest's top languages.
Methodology: both counts come from cached OctoCounts reports generated with tokei. jestjs/jest was counted at ref main (commit e95d9dbbec2a) on 2026-08-26; vitest-dev/vitest was counted at ref main (commit 732df2c2b4bc) on 2026-08-26. See the counting methodology for ignored directories and analysis options.
Evidence and next steps:
Note: code size is not code quality. OctoCounts only reports reproducible line counts and makes no claim that either project is better.
vitest-dev/vitest has more code: 92,741 code lines versus 72,097 for jestjs/jest, about 1.3x as much, based on cached OctoCounts reports as of 2026-08-26.
Not necessarily. SLOC measures size, not complexity, quality, or maintainability. A larger codebase can mean more features, more generated or vendored code, more verbose language idioms, or more tests — none of which imply the code is harder to work with. Use SLOC to gauge the scale of what you'd be reading or maintaining, not as a quality signal for jestjs/jest, vitest-dev/vitest, or any repository.
Methodology: both counts come from cached OctoCounts reports generated with tokei. jestjs/jest was counted at ref main (commit e95d9dbbec2a) on 2026-08-26; vitest-dev/vitest was counted at ref main (commit 732df2c2b4bc) on 2026-08-26. See the counting methodology for ignored directories and analysis options.
Yes. This page shows the default branch for each repository. Use the interactive comparison tool to pick any public GitHub repository, branch, tag, or commit SHA for both sides and get a fresh side-by-side report.