pola-rs/polars - Open Source PR Review Scorecard

Extremely fast Query Engine for DataFrames, written in Rust

C-Rank Grade: A (Welcoming) - 66/100

External PR Merge Rate: 64%

Response Time: -

First Timer Success: 54%

Frequently Asked Questions

Is pola-rs/polars welcoming to first-time open-source contributors?

pola-rs/polars has a recorded first-timer success rate of 54.1%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.

How fast can I expect code review feedback on my pull request?

Maintainers in pola-rs/polars respond to incoming external pull requests in approximately 0.0 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 66.5 C-Rank™ score (A Tier) represent?

The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 66.5 places pola-rs/polars in the A tier.

What is the external contributor pull request merge rate for pola-rs/polars?

The external contributor pull request merge rate for pola-rs/polars is 64.2%, based on public PR activity from non-core contributors.

Are there Good First Issues available in pola-rs/polars?

pola-rs/polars currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".

pola-rs
pola-rs/polarsA•Welcoming40.1k
GitHub
Back to Explorer
pola-rs

pola-rs/polars

40,091
Active (30d)A•Welcoming(66/100)Rust

Extremely fast Query Engine for DataFrames, written in Rust

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Constructive Code Reviewer

Warmth Score
7.4/10
Patience Score
7.8/10
Nitpick Rate
33%

Balanced & professional review environment in pola-rs/polars. Maintains strict focus on technical quality and test standards.

Top PR Submission Do's

  • •Add unit tests with >80% coverage for modified code paths
  • •Run repository linter and code formatters locally before pushing
  • •Link relevant GitHub issue ID in PR description pre-flight checklist

Top PR Friction Pitfalls (Don'ts)

  • •Do not submit unlinked PRs without referencing an existing issue
  • •Do not mix refactoring and feature logic into a single commit
  • •Do not ping maintainers repeatedly within 24 hours of opening
Response Velocity
-
No reviewer activity recorded

Average Response Latency

Tracks hours until a maintainer leaves a review, comment, or PR response.

Merge Efficiency
64.2%
Moderate PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
54.1%
Strong first-timer PR acceptance rate

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
100 core
Highly collaborative maintainer core
Diagnostic Health HUD
64.2%
Merge Gauge
54.1%
1st-Timer
Community Vibe42/100

Embed C-Rank Badge

Show contributors that your repository actively reviews and merges external pull requests.

GetMerged C-Rank badge for pola-rs/polars
[![GetMerged C-Rank](https://getmerged.abhishekco.de/api/badge/pola-rs/polars)](https://getmerged.abhishekco.de/pola-rs/polars?utm_source=github&utm_medium=badge)

Active Good First Issues (2)

View on GitHub

Checks I have checked that this issue has not already been reported. I have confirmed this bug exists on the latest version of Polars. Reproducible example import polars as pl df = pl.DataFrame({"a": [1.5, 2.5, 3.5]}) out = df.write_csv(float_scientific=True, decimal_comma=True, separator=";") # actual 'a\n1,5e0\n1,5e02,5e0\n1,5e02,5e03,5e0\n' # expected 'a\n1,5e0\n2,5e0\n3,5e0\n' Log output actual : 'a\n1,5e0\n1,5e02,5e0\n1,5e02,5e03,5e0\n' expected: 'a\n1,5e0\n2,5e0\n3,5e0\n' [{'a': '1,5e0'}, {'a': '1,5e02,5e0'}, {'a': '1,5e02,5e03,5e0'}] Traceback (most recent call last): File "/home/koen/my-polars/fuzz/findings/mre_io_csv_float_scientific_decimal_comma.py", line 19, in <module> assert out == "a\n1,5e0\n2,5e0\n3,5e0\n", "SILENT WRITER CORRUPTION" ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ AssertionError: SILENT WRITER CORRUPTION also, $ cat tt.csv a 1,5e0 1,5e02,5e0 1,5e02,5e03,5e0 Issue description Incorrect formatting. Expected behavior See repro. Installed versi

📅 Opened Sep 29, 2026💬 5 comments
Quality: 90/100Contribute

Checks I have checked that this issue has not already been reported. I have confirmed this bug exists on the latest version of Polars. Reproducible example import polars as pl tmp_path = "./tmp" df = pl.DataFrame( { "p": [10, 10, 20, 20], "a": [1, 2, 3, None], "b": [False, False, True, None] } ) df.write_delta( tmp_path, delta_write_options={"partition_by": "p"}, ) expr = pl.col.a.is_null() out = pl.scan_delta(tmp_path).filter(expr).collect() # filter works expr = pl.col.b.is_null() out = pl.scan_delta(tmp_path).filter(expr).collect() # filter does not work expr = pl.col.b == pl.lit(False) out = pl.scan_delta(tmp_path).filter(expr).collect() Log output $ POLARS_VERBOSE=1 pp issue_bool_mre.py 2>&1 | grep skipping initialize_scan_predicate: Predicate pushdown allows skipping 1 / 2 files initialize_scan_predicate: Predicate pushdown allows skipping 1 / 2 files initialize_scan_predicate: Predicate pushdown allows skipping 0 / 2 files Issue

📅 Opened Jan 26, 2026💬 8 comments
Quality: 70/100Contribute
Looking for more Rust beginner tasks?Explore Rust GFI

Contributor Community Vibe Feedback

Rate what actually matters after opening a pull request here.

Have you contributed to this repo?

Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.

3 ratings required
Maintainer helpfulness
Review speed
Beginner friendliness

Contributor Compatibility & Review Speed Analysis for pola-rs/polars

When evaluating whether to contribute to pola-rs/polars, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.

Currently, maintainers of pola-rs/polars acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 64.2% were successfully merged into the primary branch.

Frequently Asked Questions - Contributing to pola-rs/polars

01

Is pola-rs/polars welcoming to first-time open-source contributors?

pola-rs/polars has a recorded first-timer success rate of 54.1%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.

02

How fast can I expect code review feedback on my pull request?

The initial maintainer response time averages ~-. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 66.5 C-Rank™ score represent?

The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 66.5 places pola-rs/polars in the Welcoming tier.

04

What is the external contributor pull request merge rate for pola-rs/polars?

The external pull request merge rate is 64.2%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.

05

Are there beginner Good First Issues open in pola-rs/polars?

Yes, pola-rs/polars currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.

GetMerged C-Rank™ Indexing Standard

All metrics displayed for pola-rs/polars are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.