dbt enables data analysts and engineers to transform their data using the same practices that software engineers use to build applications.
C-Rank Grade: B (Solid) - 55/100
External PR Merge Rate: 35%
Response Time: 14h
First Timer Success: 30%
dbt-labs/dbt-core has a recorded first-timer success rate of 29.5%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in dbt-labs/dbt-core respond to incoming external pull requests in approximately 14.4 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 54.6 places dbt-labs/dbt-core in the B tier.
The external contributor pull request merge rate for dbt-labs/dbt-core is 34.9%, based on public PR activity from non-core contributors.
dbt-labs/dbt-core does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
Balanced & professional review environment in dbt-labs/dbt-core. Maintains strict focus on technical quality and test standards.
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/dbt-labs/dbt-core?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 05:00 UTC (05:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 04:00 to 08:00 UTC (04:00 - 08:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~9 hours (44% approval). Large PRs (>500 lines) take ~69 hours (16% approval). Keep your diff compact for rapid review.
Summary dbt Fusion's run_results.json artifact has several discrepancies compared to dbt Core's output. Since run_results.json is consumed by downstream tools (CI/CD integrations, dbt Cloud, third-party tools), these differences can cause compatibility issues. Tested with: dbt Core 1.11.7 (dbt-snowflake 1.11.3) dbt Fusion 2.0.0-preview.145 Schema version: v6 (both) Adapter: Snowflake Discrepancies 1. Missing fields on result entries Fusion result entries are missing several fields that Core always includes: Field Core behavior Fusion behavior message Always present. Human-readable summary (e.g. "SUCCESS 32", "INSERT 499", "Got 4 results, configured to fail if != 0", or full error message for failures) Missing entirely compiled Always present. true for models/tests, null for seeds Missing entirely compiled_code Always present. Contains compiled SQL for models/tests, null for seeds Missing entirely batch_results Always present (null for non-batched) Missing entirely fail
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 dbt-labs/dbt-core, 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 dbt-labs/dbt-core acknowledge new external contributions in approximately 14 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 34.9% were successfully merged into the primary branch.
dbt-labs/dbt-core has a recorded first-timer success rate of 29.5%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~14 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 54.6 places dbt-labs/dbt-core in the Solid tier.
The external pull request merge rate is 34.9%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
dbt-labs/dbt-core does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.
All metrics displayed for dbt-labs/dbt-core 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.