uv vs Poetry: source lines of code compared

The uv vs Poetry comparison on OctoCounts shows side-by-side source line counts for astral-sh/uv and python-poetry/poetry, 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 astral-sh/uv and python-poetry/poetry 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-16, astral-sh/uv contains 461,416 total lines (399,652 code) across 1,065 files, while python-poetry/poetry contains 30,995 total lines (21,421 code) across 198 files as of 2026-11-15. astral-sh/uv has about 19x the counted code lines of python-poetry/poetry 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.

Metricastral-sh/uvpython-poetry/poetry
Files1,065198
Total lines461,41630,995
Code lines399,65221,421
Comment lines27,0763,568
Blank lines34,6886,006
Languages counted164

Top languages in astral-sh/uv: Rust (63.3% of code), JSON (30.0% of code), YAML (3.0% of code). Top languages in python-poetry/poetry: Python (97.2% of code), JSON (1.9% of code), TOML (0.9% of code). JSON, Python, TOML appear in both top language lists; Rust, YAML appear only in astral-sh/uv's top languages; Markdown appears only in python-poetry/poetry's top languages.

Methodology: both counts come from cached OctoCounts reports generated with tokei. astral-sh/uv was counted at ref main (commit cf9bace0e30e) on 2026-11-16; python-poetry/poetry was counted at ref main (commit 18668c8dacdb) on 2026-11-15. 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. astral-sh/uv: 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. python-poetry/poetry: 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.

About this comparison

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: astral-sh/uv is the uv repository — the Rust-based Python package installer and resolver and the surrounding tooling in the same project — while python-poetry/poetry is the Poetry repository, the Python-based packaging and dependency-management tool with its own installer and resolver. Both repositories cover the tool itself rather than any environment it manages, taken on the dates in the methodology line above.

The per-language tables make the headline contrast measurable: uv is a predominantly Rust codebase while Poetry is a Python application — two implementations of the same category of tool in different languages, without needing to infer anything from totals.

A larger or smaller source tree does not measure install or resolution speed: performance is a property of the shipped tool's design and the package set being resolved, not of the repository's line count.

Sources: astral-sh/uv repository (Rust Python tooling) · python-poetry/poetry 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.

Compare FAQ

Which has more lines of code, astral-sh/uv or python-poetry/poetry?

As of 2026-11-16, astral-sh/uv contains 461,416 total lines (399,652 code) across 1,065 files, while python-poetry/poetry contains 30,995 total lines (21,421 code) across 198 files as of 2026-11-15. astral-sh/uv has about 19x the counted code lines of python-poetry/poetry 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.

Does more source lines of code mean more complexity?

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 astral-sh/uv, python-poetry/poetry, or any repository.

How is this comparison calculated?

Methodology: both counts come from cached OctoCounts reports generated with tokei. astral-sh/uv was counted at ref main (commit cf9bace0e30e) on 2026-11-16; python-poetry/poetry was counted at ref main (commit 18668c8dacdb) on 2026-11-15. See the counting methodology for ignored directories and analysis options.

Can I compare a different branch, tag, or commit?

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.