The first Scala macros' standard library
C-Rank Grade: B (Solid) - 41/100
External PR Merge Rate: 38%
Response Time: 16d
First Timer Success: 50%
kubuszok/hearth has a recorded first-timer success rate of 50.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in kubuszok/hearth respond to incoming external pull requests in approximately 393.1 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 41.3 places kubuszok/hearth in the B tier.
The external contributor pull request merge rate for kubuszok/hearth is 38.0%, based on public PR activity from non-core contributors.
kubuszok/hearth currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Growing Scala project in kubuszok/hearth 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/kubuszok/hearth?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 15:00 UTC (15:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 14:00 to 18:00 UTC (14:00 - 18:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~255 hours (47% approval). Large PRs (>500 lines) take ~1887 hours (17% approval). Keep your diff compact for rapid review.
We should figure out a way of getting rid of the adapter boilerplate as seen in https://scala-hearth.readthedocs.io/en/latest/basic-utilities/#your-first-hearth-based-macro, e.g. // Scala 2 - macro annotations? @GenerateAdapters("yourMacro" -> "yourMacroImpl") class YourMacro(val c: blackbox.Context) extends hearth.MacroCommonsScala2 with SharedMacroLogic // Scala 3 - compiler plugin? @GenerateAdapters("yourMacro") class YourMacro(q: Quotes) extends hearth.MacroCommonsScala3(using q), SharedMacroLogic
Consider using context function in DirectStyle on Scala 3 and some macro(?) on Scala 2 perhaps macros doing something like: https://scastie.scala-lang.org/MateuszKubuszok/QehectftSjyFRiABm8zWsw/2 ? fallback to the current syntax should be possible in case sth isn't working (Issue extracted from #85).
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 kubuszok/hearth, 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 kubuszok/hearth acknowledge new external contributions in approximately 16 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 38.0% were successfully merged into the primary branch.
kubuszok/hearth has a recorded first-timer success rate of 50.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~16 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 41.3 places kubuszok/hearth in the Solid tier.
The external pull request merge rate is 38.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, kubuszok/hearth currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for kubuszok/hearth 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.