🪐 Markdown with superpowers: from ideas to papers, presentations, websites, books, and knowledge bases.
C-Rank Grade: S (Elite) - 70/100
External PR Merge Rate: 93%
Response Time: 1d
First Timer Success: 100%
iamgio/quarkdown has a recorded first-timer success rate of 100.0%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in iamgio/quarkdown respond to incoming external pull requests in approximately 27.7 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 70.2 places iamgio/quarkdown in the S tier.
The external contributor pull request merge rate for iamgio/quarkdown is 93.3%, based on public PR activity from non-core contributors.
iamgio/quarkdown currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in iamgio/quarkdown. Prompt code reviews with positive guidance for new contributors.
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/iamgio/quarkdown?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 13:00 UTC (13:00 UTC in your timezone). Recommended submission window is Monday - Thursday from 11:00 to 15:00 UTC (11:00 - 15:00 UTC local).
Limited recent maintainer review activity recorded for this repository. Prediction based on heuristic baseline.
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~18 hours (96% approval). Large PRs (>500 lines) take ~133 hours (42% approval). Keep your diff compact for rapid review.
Enter your branch size and test coverage below to forecast review turnaround and get 1-click git splitting commands.
Alternative open-source projects with active maintainers in Kotlin.
Bring the native Dynamic Island experience to HyperOS. Bridges android notifications into HyperIslands.
Comprehensive Bitcoin development library for Android, implemented on Kotlin. SPV wallet implementation for Bitcoin, Bitcoin Cash, Litecoin and Dash blockchains. Fully compliant with existing standards and BIPs.
Wireless Helper for Headuint Revived
Before submitting I am using the latest version of Quarkdown. I have checked the wiki to confirm this feature doesn't already exist. I have searched existing issues for duplicates. Description I would want .totalpages to also be affected by .resetpagenumber. Consider this scenario where I don't want a numbering on the title page: .doctype {paged} .center #! Title Page .pagebreak # First content page .pagemargin {bottomcenter} .currentpage / .totalpages .resetpagenumber # Second content page # Third content page I want the page numbering to range from 1/3 to 3/3. Instead it ranges from 1/4 to 3/4. Proposed syntax or behavior A relatively easy and backwards-compatible fix would be to allow .totalpages to have an optional argument being one of document | section with document being the default. document will act as the .totalpages-command just as before section will be the number of pages starting from either the last .resetpagenumber-command (considering the start argu
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 iamgio/quarkdown, 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 iamgio/quarkdown acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 93.3% were successfully merged into the primary branch.
iamgio/quarkdown has a recorded first-timer success rate of 100.0%. Repositories ranked Elite 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 70.2 places iamgio/quarkdown in the Elite tier.
The external pull request merge rate is 93.3%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, iamgio/quarkdown 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 iamgio/quarkdown 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.