The Jest vs Vitest comparison on OctoCounts shows side-by-side source line counts for jestjs/jest and vitest-dev/vitest, counted under the rules and on the dates stated below: files, total lines, code lines, comment lines, blank lines, and per-language totals, pinned to the exact commits listed below.
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-11-11, jestjs/jest contains 152,905 total lines (72,289 code) across 1,691 files, while vitest-dev/vitest contains 123,764 total lines (95,729 code) across 771 files as of 2026-11-16. vitest-dev/vitest has about 1.3x the counted code lines of jestjs/jest under the same engine and counting rules. 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,691 | 771 |
| Total lines | 152,905 | 123,764 |
| Code lines | 72,289 | 95,729 |
| Comment lines | 52,593 | 15,468 |
| Blank lines | 28,023 | 12,567 |
| Languages counted | 15 | 11 |
Top languages in jestjs/jest: TypeScript (78.0% of code), JavaScript (11.2% of code), JSON (9.2% of code). Top languages in vitest-dev/vitest: TypeScript (77.5% of code), YAML (18.0% of code), JSON (1.8% 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 aa88f7cf0bfc) on 2026-11-11; vitest-dev/vitest was counted at ref main (commit efba8cbfe94b) on 2026-11-16. See the counting methodology for ignored directories and analysis options.
Both reports use the same engine and effective counting rules. Repository declarations, when enabled, are specific to each repository. jestjs/jest: 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. vitest-dev/vitest: 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.
Background observations recorded on 2026-09-16; language descriptions here are historical context, not claims about the current filtered shares. Use this page's measured language breakdown for current counts. Repository layout before counting filters: jestjs/jest is the Jest monorepo: the test runner, expect matchers, mocking and snapshot machinery, reporters, and the family of packages around them. vitest-dev/vitest is the Vitest repository: the runner and its core integrations, written in TypeScript. Both repositories are test-runner source trees, counted on the dates in the methodology line; the broader ecosystems and environment adapters for both tools live partly elsewhere.
These counts do not predict test execution speed, memory use, or which runner fits a project; those depend on the runner version, the transform and environment setup, and the test suite itself. Read the numbers as the maintenance surface of each tool.
Sources: jestjs/jest repository (packages monorepo) · vitest-dev/vitest repository. Statements verified 2026-09-16.
Evidence and next steps:
Saved reports remain subject to cache cleanup and replacement. Export their JSON for durable citation; live report URLs can change.
Note: code size is not code quality. OctoCounts only reports reproducible line counts and makes no claim that either project is better.
As of 2026-11-11, jestjs/jest contains 152,905 total lines (72,289 code) across 1,691 files, while vitest-dev/vitest contains 123,764 total lines (95,729 code) across 771 files as of 2026-11-16. vitest-dev/vitest has about 1.3x the counted code lines of jestjs/jest under the same engine and counting rules. Code size is not code quality: a larger count only means more source material, not a better or worse project.
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 aa88f7cf0bfc) on 2026-11-11; vitest-dev/vitest was counted at ref main (commit efba8cbfe94b) on 2026-11-16. 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.