Ergonomic bindings to duckdb for Rust
C-Rank Grade: A (Welcoming) - 63/100
External PR Merge Rate: 61%
Response Time: 17h
First Timer Success: 50%
duckdb/duckdb-rs has a recorded first-timer success rate of 50.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in duckdb/duckdb-rs respond to incoming external pull requests in approximately 16.9 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
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 63.4 places duckdb/duckdb-rs in the A tier.
The external contributor pull request merge rate for duckdb/duckdb-rs is 60.7%, based on public PR activity from non-core contributors.
duckdb/duckdb-rs currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Growing Rust project in duckdb/duckdb-rs welcoming community pull requests and bug fixes.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/duckdb/duckdb-rs?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 08:00 UTC (08:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 08:00 to 12:00 UTC (08:00 - 12:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~11 hours (76% approval). Large PRs (>500 lines) take ~81 hours (27% approval). Keep your diff compact for rapid review.
First of all, thanks for maintaining this crate 🚀 I wanted to check something with people that might be more familiar with inner workings of this crate (or duckdb for that matter): I have a use-case where I export data from Snowflake to S3, and then ingest that data into in-memory duckdb, using ducdkb-rs crate. Everything is fine and all, but I am not sure what is the best way to handle scenario where there is no data in original Snowflake table: in that case Snowflake does not create empty parquet file, it doesn't do anything really. If that happens, currently I get an Error result, and I figured out from error messages that it it kinda looks like something this f-on should return true for: fn is_http_404_error(msg: &str) -> bool { let msg = msg.to_lowercase(); msg.starts_with("http error") && msg.ends_with("404 (not found).") } As far as I remember, the actual instance is duckdb::Error::DuckDBFailure, not sure about ErrorCode though. I have a test suite that started failin
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to duckdb/duckdb-rs, 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 duckdb/duckdb-rs acknowledge new external contributions in approximately 16 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 60.7% were successfully merged into the primary branch.
duckdb/duckdb-rs has a recorded first-timer success rate of 50.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~16 hours. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
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 63.4 places duckdb/duckdb-rs in the Welcoming tier.
The external pull request merge rate is 60.7%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, duckdb/duckdb-rs currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for duckdb/duckdb-rs 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.