Mergin Maps mobile app 📲 Open QGIS projects and manage vector data on your phone, even offline 📶 (Android/iOS/Windows app)
C-Rank Grade: A (Welcoming) - 61/100
External PR Merge Rate: 72%
Response Time: 17h
First Timer Success: 60%
MerginMaps/mobile has a recorded first-timer success rate of 60.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in MerginMaps/mobile respond to incoming external pull requests in approximately 17.4 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 61.4 places MerginMaps/mobile in the A tier.
The external contributor pull request merge rate for MerginMaps/mobile is 71.6%, based on public PR activity from non-core contributors.
MerginMaps/mobile currently has 7 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
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/MerginMaps/mobile?utm_source=github&utm_medium=badge)
Enter your branch size and test coverage below to forecast review turnaround and get 1-click git splitting commands.
Alternative open-source projects with active maintainers in C++.
Vega Strike Engine
Read the wired or wireless mbus protocol to acquire utility meter readings.
Monero: the secure, private, untraceable cryptocurrency
This repository currently has 7 open good first issue tickets available for newcomers.
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 MerginMaps/mobile, 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 MerginMaps/mobile acknowledge new external contributions in approximately 17 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 71.6% were successfully merged into the primary branch.
MerginMaps/mobile has a recorded first-timer success rate of 60.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~17 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 61.4 places MerginMaps/mobile in the Welcoming tier.
The external pull request merge rate is 71.6%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, MerginMaps/mobile currently has 7 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for MerginMaps/mobile 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.