This page compares the source lines of code (SLOC) of gohugoio/hugo and jekyll/jekyll 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, gohugoio/hugo contains 253,710 total lines (181,215 code) across 1,104 files, while jekyll/jekyll contains 58,705 total lines (28,177 code) across 699 files as of 2026-09-03. gohugoio/hugo is about 6.4x the size of jekyll/jekyll by code lines. Code size is not code quality: a larger count only means more source material, not a better or worse project.
| Metric | gohugoio/hugo | jekyll/jekyll |
|---|---|---|
| Files | 1,104 | 699 |
| Total lines | 253,710 | 58,705 |
| Code lines | 181,215 | 28,177 |
| Comment lines | 37,302 | 20,924 |
| Blank lines | 35,193 | 9,604 |
| Languages counted | 12 | 12 |
Top languages in gohugoio/hugo: Go (94.5% of code), JavaScript (2.0% of code), C (2.0% of code). Top languages in jekyll/jekyll: Ruby (60.0% of code), Gherkin (Cucumber) (16.2% of code), Sass (7.5% of code). JavaScript, YAML appear in both top language lists; Go, C, HTML appear only in gohugoio/hugo's top languages; Ruby, Gherkin (Cucumber), Sass appear only in jekyll/jekyll's top languages.
Methodology: both counts come from cached OctoCounts reports generated with tokei. gohugoio/hugo was counted at ref master (commit 166d3ee1ce94) on 2026-08-26; jekyll/jekyll was counted at ref master (commit 74d751339d3e) on 2026-09-03. 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.
gohugoio/hugo has more code: 181,215 code lines versus 28,177 for jekyll/jekyll, about 6.4x as much, based on cached OctoCounts reports as of 2026-09-03.
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 gohugoio/hugo, jekyll/jekyll, or any repository.
Methodology: both counts come from cached OctoCounts reports generated with tokei. gohugoio/hugo was counted at ref master (commit 166d3ee1ce94) on 2026-08-26; jekyll/jekyll was counted at ref master (commit 74d751339d3e) on 2026-09-03. 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.