Configurable HTML, Vue, Svelte, Astro, Angular, Jinja, Twig, Nunjucks, Vento, Mustache, Handlebars and XML formatter with dprint integration.
C-Rank Grade: A (Welcoming) - 57/100
External PR Merge Rate: 86%
Response Time: 8d
First Timer Success: 100%
g-plane/markup_fmt has a recorded first-timer success rate of 100.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in g-plane/markup_fmt respond to incoming external pull requests in approximately 199.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 57.1 places g-plane/markup_fmt in the A tier.
The external contributor pull request merge rate for g-plane/markup_fmt is 85.7%, based on public PR activity from non-core contributors.
g-plane/markup_fmt currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in g-plane/markup_fmt. Reviews community pull requests with focus on project quality.
Discussions in g-plane/markup_fmt focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.
Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.
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/g-plane/markup_fmt?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 Monday - Wednesday from 00:00 to 04:00 UTC (00:00 - 04:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~130 hours (96% approval). Large PRs (>500 lines) take ~958 hours (39% approval). Keep your diff compact for rapid review.
The bug The formatter adds infinite indentation to the body of CSS styles in Svelte components. Both markup_fmt and malva plugs are used. Original file contents: <style> /* malva-ignore */ div { color: red; } </style> After running the formatter: <style> /* malva-ignore */ div { color: red; } </style> After running the formatter again: <style> /* malva-ignore */ div { color: red; } </style> The two lines below div { are indented on every formatter pass. Removing the /* malva-ignore */ comment or leaving the body empty resolves the issue. color: red; was chosen arbitrarily; anything in the body reproduces the bug. This only happens in the style block of Svelte files; this problem is not present in regular CSS files. How to reproduce package.json { "name": "dprint-malva-bug-demo", "private": true, "version": "0.0.1", "type": "module", "scripts": { "fmt": "dprint fmt" }, "devDependencies": { "dprint": "^0.51.1" } } dprint.json { "markup": {
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 g-plane/markup_fmt, 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 g-plane/markup_fmt acknowledge new external contributions in approximately 8 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 85.7% were successfully merged into the primary branch.
g-plane/markup_fmt has a recorded first-timer success rate of 100.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~8 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 57.1 places g-plane/markup_fmt in the Welcoming tier.
The external pull request merge rate is 85.7%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, g-plane/markup_fmt 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 g-plane/markup_fmt 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.