DaCe - Data Centric Parallel Programming
C-Rank Grade: A (Welcoming) - 65/100
External PR Merge Rate: 60%
Response Time: 1d
First Timer Success: 64%
spcl/dace has a recorded first-timer success rate of 63.6%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in spcl/dace respond to incoming external pull requests in approximately 26.0 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 65.0 places spcl/dace in the A tier.
The external contributor pull request merge rate for spcl/dace is 60.0%, based on public PR activity from non-core contributors.
spcl/dace currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Responsive & active maintainer team in spcl/dace. Reviews pull requests with focus on project architectural goals.
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/spcl/dace?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 14:00 UTC (14:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 14:00 to 18:00 UTC (14:00 - 18:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~17 hours (75% approval). Large PRs (>500 lines) take ~125 hours (27% approval). Keep your diff compact for rapid review.
Data descriptors expose total_size, but there is no total_elements. Array.total_size is the allocated span, which can exceed the logical element count when strides or padding are given, so callers that need the number of elements recompute prod(shape) themselves. Proposal: add a total_elements property to dace.data (at least Data, Array, Scalar, Stream), with Scalar returning 1, so that total_elements and total_size are both valid on every descriptor, scalars included.
replace / replace_dict are typed Dict[str, str], but some callers pass other types. symbolic.safe_replace hands its callback sympy symbols (default value_as_string=False), and LoopUnroll passes the loop index as a number. #2583 converts these back with str() where names are stored (LoopRegion.loop_variable, interstate edge assignment keys). That also silently stores non-identifiers such as "3". Proposal: remove the str() casts, make replace/replace_dict reject non-string replacement values, and fix the offending callers at the source. This touches many call sites and needs a full CI run (see the discussion in #2583).
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 spcl/dace, 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 spcl/dace acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 60.0% were successfully merged into the primary branch.
spcl/dace has a recorded first-timer success rate of 63.6%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~1 days+. 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 65.0 places spcl/dace in the Welcoming tier.
The external pull request merge rate is 60.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, spcl/dace 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 spcl/dace 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.