Multi-Mission Geographic Information System - A Web-based Mapping and Spatial Data Infrastructure for Earth, Lunar and Planetary Visualization, Research, Science, Planning and Operations.
C-Rank Grade: A (Welcoming) - 67/100
External PR Merge Rate: 78%
Response Time: 1d
First Timer Success: 100%
NASA-AMMOS/MMGIS 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 NASA-AMMOS/MMGIS respond to incoming external pull requests in approximately 24.2 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 66.7 places NASA-AMMOS/MMGIS in the A tier.
The external contributor pull request merge rate for NASA-AMMOS/MMGIS is 78.3%, based on public PR activity from non-core contributors.
NASA-AMMOS/MMGIS currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Multi-Mission Geographic Information System - A Web-based Mapping and Spatial Data Infrastructure for Earth, Lunar and Planetary Visualization, Research, Science, Planning and Operations.
Active maintainer team in NASA-AMMOS/MMGIS 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/NASA-AMMOS/MMGIS?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 18:00 UTC (18: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 ~16 hours (96% approval). Large PRs (>500 lines) take ~116 hours (35% approval). Keep your diff compact for rapid review.
As a user, when I mouse over the map with the Identifier Tool active, I want to see the layer's respective legends in the Legend Tool also highlighted. Do note that while plugins cannot depend on each other, it is still in the patten that they can check for the presence of another plugin and behave and call the other accordingly -- they just must not assume the other plugin is always there or enabled.
In the Coordinates Tab of /configure under the Projection Setup subheading, the "Path to Basemap tilemapresource.xml or ArcGIS MapServer" field is duplicated twice. It should only appear once. In addition, the Projection Setup subheading should include a description or some graphical/UI way to better indicate that these are just helper actions to help admins quickly set up the above projection fields. The issue now is that quite a few admins believe that, say, the TileMatrixSet needs to be set properly and influences the config (again, it's just a field so that an admin can use the convenient actions buttons to the right of it.)
Currently a lot of MMGIS' new documentation is tailored for an Agentic Developer, one setting up MMGIS, developing new plugins, and so on. Another persona an agent may take is that of an administrator and the agent-specific documentation for that role is far less developed. For instance: asking AI to stand up a new mission and just include the following DEM (https://zenodo.org/records/22164484) is not as smooth as it could be: The agent does not know it has to look at a series of plugin jsons to know how to construct a config json object. The agent does not immediately know that it should be in a non-coding capacity While the agent knows how to setup MMGIS, over longer sessions it often forgets its admin password to the /configure and has to waste time trying to reset it in the database How to configure projections was less clear to the agent in the case of the DEM above (it did not know Venus projection tilematrixset were already provided via planetcantile) and so on. I good way to
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 NASA-AMMOS/MMGIS, 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 NASA-AMMOS/MMGIS acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 78.3% were successfully merged into the primary branch.
NASA-AMMOS/MMGIS 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 ~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 66.7 places NASA-AMMOS/MMGIS in the Welcoming tier.
The external pull request merge rate is 78.3%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, NASA-AMMOS/MMGIS currently has 3 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for NASA-AMMOS/MMGIS 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.