One framework for creating powerful cross-platform games.
C-Rank Grade: A (Welcoming) - 66/100
External PR Merge Rate: 70%
Response Time: 10h
First Timer Success: 82%
MonoGame/MonoGame has a recorded first-timer success rate of 81.8%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in MonoGame/MonoGame respond to incoming external pull requests in approximately 9.6 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.9 places MonoGame/MonoGame in the A tier.
The external contributor pull request merge rate for MonoGame/MonoGame is 70.2%, based on public PR activity from non-core contributors.
MonoGame/MonoGame currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Balanced & professional review environment in MonoGame/MonoGame. Maintains strict focus on technical quality and test standards.
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/MonoGame/MonoGame?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 17:00 UTC (17:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 16:00 to 20:00 UTC (16:00 - 20:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~6 hours (88% approval). Large PRs (>500 lines) take ~46 hours (32% approval). Keep your diff compact for rapid review.
We have a few missing transform methods in Vector4 that are throwing NotImplementedExceptions: MonoGame/MonoGame.Framework/Vector4.cs Line 1090 in 040d31d public static void Transform(ref Vector3 value, ref Quaternion rotation, out Vector4 result) MonoGame/MonoGame.Framework/Vector4.cs Line 1119 in 040d31d public static void Transform(ref Vector4 value, ref Quaternion rotation, out Vector4 result)
Prerequisites I have verified this issue is present in the develop branch I have searched open and closed issues to ensure it has not already been reported. MonoGame Version 3.8.4.1 Which MonoGame platform are you using? MonoGame Cross-Platform Desktop Application (mgdesktopgl) Operating System Mac Description Wine is being removed from homebrew on the 2026-09-01 https://bugs.winehq.org/show_bug.cgi?id=58946 We need a solution which will allow DesktopGL users to still compile and run on MacOS after this. We need to research the best way forward and implement it before the deadline. This is quite urgent. Steps to Reproduce Install wine via homebrew, you will see the deprecation notice. Minimal Example Repo No response Expected Behavior We need a way to compile effects on MacOS (and linux?). Resulting Behavior after 2026-09-01 MacOS users will no longer be able to compile effects. Files No response
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 MonoGame/MonoGame, 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 MonoGame/MonoGame acknowledge new external contributions in approximately 9 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 70.2% were successfully merged into the primary branch.
MonoGame/MonoGame has a recorded first-timer success rate of 81.8%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~9 hours. 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.9 places MonoGame/MonoGame in the Welcoming tier.
The external pull request merge rate is 70.2%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, MonoGame/MonoGame 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 MonoGame/MonoGame 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.