PKMDS: Pokémon Save Editor for Web (no support for game hacks)
C-Rank Grade: A (Welcoming) - 57/100
External PR Merge Rate: 94%
Response Time: 11d
First Timer Success: 100%
codemonkey85/PKMDS-Blazor 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 codemonkey85/PKMDS-Blazor respond to incoming external pull requests in approximately 266.8 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.4 places codemonkey85/PKMDS-Blazor in the A tier.
The external contributor pull request merge rate for codemonkey85/PKMDS-Blazor is 94.1%, based on public PR activity from non-core contributors.
codemonkey85/PKMDS-Blazor currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Strict review standards in codemonkey85/PKMDS-Blazor. 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/codemonkey85/PKMDS-Blazor?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 00:00 UTC (00:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 13:00 to 17:00 UTC (13:00 - 17:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~173 hours (96% approval). Large PRs (>500 lines) take ~1281 hours (42% approval). Keep your diff compact for rapid review.
Create a debug / develop only control that dynamically lists all of the save files in the TestFiles directory and lets you load any one of them with one click. While we're at it, rename the files to normalize the names.
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 codemonkey85/PKMDS-Blazor, 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 codemonkey85/PKMDS-Blazor acknowledge new external contributions in approximately 11 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 94.1% were successfully merged into the primary branch.
codemonkey85/PKMDS-Blazor 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 ~11 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.4 places codemonkey85/PKMDS-Blazor in the Welcoming tier.
The external pull request merge rate is 94.1%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, codemonkey85/PKMDS-Blazor 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 codemonkey85/PKMDS-Blazor 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.