🐍🎮 pygame - Community Edition is a FOSS Python library for multimedia applications (like games). Built on top of the excellent SDL library.
C-Rank Grade: A (Welcoming) - 57/100
External PR Merge Rate: 32%
Response Time: 5h
First Timer Success: 38%
pygame-community/pygame-ce has a recorded first-timer success rate of 38.5%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in pygame-community/pygame-ce respond to incoming external pull requests in approximately 4.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 56.8 places pygame-community/pygame-ce in the A tier.
The external contributor pull request merge rate for pygame-community/pygame-ce is 32.1%, based on public PR activity from non-core contributors.
pygame-community/pygame-ce currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Active maintainer team in pygame-community/pygame-ce welcoming community pull requests and bug fixes.
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/pygame-community/pygame-ce?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 22:00 UTC (22:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 20:00 to 00:00 UTC (20:00 - 00:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (40% approval). Large PRs (>500 lines) take ~22 hours (15% approval). Keep your diff compact for rapid review.
https://github.com/pygame-community/pygame-ce/blob/main/src_c/font.c#L1288 The default font gets shrunk sometimes when it's loaded, this is a weird behavior that defies all explanation and should go away in 3.0
Summary Remove the redundant catch-all implementation stubs that follow @overload declarations in buildconfig/stubs/pygame/color.pyi. Rationale A stub file does not need a concrete implementation declaration after a complete overload set. The catch-all def ...(*args) -> Color declaration weakens the type information and is inconsistent with the intended overload-only API description. Affected declarations Color.from_cmy Color.from_hsva Color.from_hsla Color.from_i1i2i3 Color.from_normalized Required changes Remove each @classmethod # type: ignore and def from_... (cls, *args) -> Color: # type: ignore declaration. Preserve the method docstring by attaching it to an overload declaration or by using the project’s established stub documentation pattern. The new Color.from_oklab and Color.from_oklch declarations in PR #3882 are removing the same pattern and are not part of this follow-up. Acceptance criteria Each affected Color.from_* method retains complete overload signatures. No a
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 pygame-community/pygame-ce, 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 pygame-community/pygame-ce acknowledge new external contributions in approximately 4 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 32.1% were successfully merged into the primary branch.
pygame-community/pygame-ce has a recorded first-timer success rate of 38.5%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~4 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 56.8 places pygame-community/pygame-ce in the Welcoming tier.
The external pull request merge rate is 32.1%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, pygame-community/pygame-ce currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for pygame-community/pygame-ce 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.