Discofork
Repository brief

pola-rs/polars

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis
cached 2026-03-30T15:47:48.696Z
1mo ago

pola-rs/polars

Polars is a large, active Rust-based DataFrame query engine with Python, Rust, Node.js, R, and SQL front ends. It focuses on fast lazy/eager execution, streaming for larger-than-RAM data, query optimization, multithreading, SIMD, and an Arrow columnar foundation. The repo is clearly maintained and high-traffic, with 37,923 stars, 2,713 forks, and commits landing on 2026-03-30.

GitHub
Loading tags...
Stars37,923
Forks2,713
Default branchmain
Last pushed2026-03-30T15:41:01Z
Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs
Selected

Choose this fork if you specifically need the custom CDC/Parquet/Arrow work and can own the maintenance burden. Choose upstream if you want the broader Polars feature set, faster bugfix uptake, and lower compatibility risk.

Choose this fork if your goal is HF sink wheel build automation and you want to stay close to upstream Polars. Choose upstream instead if you need the latest fixes, features, and release cadence with less maintenance overhead.

Prefer upstream unless you specifically need this older, patched 2023-era Polars behavior. For new work, this fork is too stale and too far diverged to be a safe default.

Prefer this fork only if you need its custom execution or API changes and are willing to maintain divergence. If you want the newest stable Polars behavior, documentation, and regression coverage, upstream is the safer default.

Choose this fork only if you specifically need its older, customized Polars behavior. For most adopters, upstream Polars is the safer choice because this fork is stale and materially behind current fixes and maintenance.

Choose this fork only if you want a frozen, customized Polars snapshot and are willing to maintain it yourself. If you want current performance, fixes, and lower integration risk, upstream is the better choice.

Prefer upstream unless you explicitly need a legacy 2022 Polars baseline. This fork is useful for old-API compatibility or historical patching, but it is far behind upstream and likely to miss many modern performance, SQL, Python, and streaming improvements.

Choose this fork only if you specifically need its custom Excel or internal workflow changes and can accept substantial lag from upstream. For most adopters, upstream Polars is the safer choice because this fork is old, highly diverged, and likely missing many newer fixes and improvements.

Choose this fork only if you want a heavily customized Polars base and are prepared to maintain it yourself. For most adopters, upstream is the better default because this fork is stale and materially out of date.

Choose this fork only if you specifically need its older Python/DataFrame API behavior or its custom rewrites. For most users, upstream Polars is the better default because this fork is stale, heavily divergent, and likely missing many later fixes and features.