This page compares the source lines of code (SLOC) of celery/celery and rq/rq 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, celery/celery contains 110,780 total lines (87,559 code) across 478 files, while rq/rq contains 14,437 total lines (10,939 code) across 55 files as of 2026-08-26. celery/celery is about 8.0x the size of rq/rq by code lines. Code size is not code quality: a larger count only means more source material, not a better or worse project.
| Metric | celery/celery | rq/rq |
|---|---|---|
| Files | 478 | 55 |
| Total lines | 110,780 | 14,437 |
| Code lines | 87,559 | 10,939 |
| Comment lines | 4,782 | 1,272 |
| Blank lines | 18,439 | 2,226 |
| Languages counted | 12 | 7 |
Top languages in celery/celery: Python (90.7% of code), ReStructuredText (4.6% of code), JSON (2.8% of code). Top languages in rq/rq: Python (98.2% of code), TOML (1.2% of code), INI (0.4% of code). Python appears in both top language lists; ReStructuredText, JSON, Shell, YAML appear only in celery/celery's top languages; TOML, INI, Makefile, Dockerfile appear only in rq/rq's top languages.
Methodology: both counts come from cached OctoCounts reports generated with tokei. celery/celery was counted at ref main (commit d6fa93d12a70) on 2026-08-26; rq/rq was counted at ref master (commit e1b13ffb08fd) 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.
celery/celery has more code: 87,559 code lines versus 10,939 for rq/rq, about 8.0x 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 celery/celery, rq/rq, or any repository.
Methodology: both counts come from cached OctoCounts reports generated with tokei. celery/celery was counted at ref main (commit d6fa93d12a70) on 2026-08-26; rq/rq was counted at ref master (commit e1b13ffb08fd) 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.