Code formatter for Scala
C-Rank Grade: A (Welcoming) - 65/100
External PR Merge Rate: 89%
Response Time: 4d
First Timer Success: 50%
scalameta/scalafmt 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 scalameta/scalafmt respond to incoming external pull requests in approximately 93.5 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.2 places scalameta/scalafmt in the A tier.
The external contributor pull request merge rate for scalameta/scalafmt is 89.2%, based on public PR activity from non-core contributors.
scalameta/scalafmt currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Strict review standards in scalameta/scalafmt. Ensure PR scope matches issue requirements closely before requesting review.
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/scalameta/scalafmt?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 01:00 UTC (01:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 22:00 to 02:00 UTC (22:00 - 02:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~61 hours (96% approval). Large PRs (>500 lines) take ~449 hours (40% approval). Keep your diff compact for rapid review.
This is a feature request, not an issue, so I've removed the required sections as they don't apply to this case. All the cool kids are using Typst for writing their books and stuff. It's like Latex but has a language that's not stuck in 1978. Amazing. Typst supports raw blocks with the same syntax as Markdown code fences. It would be handy if scalafmt could format these blocks in the same way it formats Markdown. I think this could reuse the same code path as Markdown, with a few changes (e.g. an addition to FileOps to recognize the .typ extension.) Is this of interest to scalafmt?
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 scalameta/scalafmt, 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 scalameta/scalafmt acknowledge new external contributions in approximately 3 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 89.2% were successfully merged into the primary branch.
scalameta/scalafmt 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 ~3 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.2 places scalameta/scalafmt in the Welcoming tier.
The external pull request merge rate is 89.2%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, scalameta/scalafmt 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 scalameta/scalafmt 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.