A Python interface for the Generic Mapping Tools.
C-Rank Grade: A (Welcoming) - 67/100
External PR Merge Rate: 79%
Response Time: 6h
First Timer Success: 67%
GenericMappingTools/pygmt has a recorded first-timer success rate of 66.7%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in GenericMappingTools/pygmt respond to incoming external pull requests in approximately 6.0 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 67.0 places GenericMappingTools/pygmt in the A tier.
The external contributor pull request merge rate for GenericMappingTools/pygmt is 79.1%, based on public PR activity from non-core contributors.
GenericMappingTools/pygmt currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in GenericMappingTools/pygmt. 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/GenericMappingTools/pygmt?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 08:00 UTC (08:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 06:00 to 10:00 UTC (06:00 - 10:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (96% approval). Large PRs (>500 lines) take ~29 hours (36% approval). Keep your diff compact for rapid review.
We already have a good tutorial for Cartesian Histograms at https://www.pygmt.org/0.19.0/tutorials/advanced/cartesian_histograms.html, which was initially developed more than 3 years ago (#2445). Here are some ideas to improve the tutorial: The series parameter is one of the most important parameters that controls the histogram, but it's not explained well. The first subsection should focus on this parameter Inspired by matplotlib's hist method's histype parameter, I feel we should have a subsection showing different histogram styles, by different combinations of fill/pen/stairs (xref: #4884 (comment)). With this subsection, we could remove the existing "Stair-steps" subsection from the tutorial Horizontal histograms are less commonly used, so it makes little sense to have "Vertical and horizontal bars" at the start of the tutorial Maybe also add a subsection for adding the distribution curves
After redesigning the PyGMT documentation landing page and the project README (#4746), I feel it is a good time to further improve the documentation. Below are some documentation issues and ideas that we can discuss and address. Improve version information shown in the footer. At the site footer, the dev version shows "Revision f8d331f" and the release version shows "Revision v0.19.0". I think it would be clearer to show "Release 0.19.0" instead of "Revision v0.19.0" for release versions. Improve the "Full installation" page Add an introductory note at the beginning, for example: #4907 The "Quickstart" section provides the fastest way to install PyGMT, whereas the following sections provide more detailed, step-by-step instructions for users with different setups or those who want to install the latest development version. List both required and optional dependencies (#4807). Improve the "PyGMT Ecosystem" page #4911 The page currently starts with "PyGMT provides a Python
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 GenericMappingTools/pygmt, 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 GenericMappingTools/pygmt acknowledge new external contributions in approximately 5 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 79.1% were successfully merged into the primary branch.
GenericMappingTools/pygmt has a recorded first-timer success rate of 66.7%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~5 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 67.0 places GenericMappingTools/pygmt in the Welcoming tier.
The external pull request merge rate is 79.1%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, GenericMappingTools/pygmt 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 GenericMappingTools/pygmt 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.