MerginMaps/mobile - Open Source PR Review Scorecard

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) - 69/100

External PR Merge Rate: 62%

Response Time: -

First Timer Success: 100%

Frequently Asked Questions

Is MerginMaps/mobile welcoming to first-time open-source contributors?

MerginMaps/mobile 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.

How fast can I expect code review feedback on my pull request?

Maintainers in MerginMaps/mobile respond to incoming external pull requests in approximately 0.0 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 68.6 C-Rank™ score (A Tier) represent?

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 68.6 places MerginMaps/mobile in the A tier.

What is the external contributor pull request merge rate for MerginMaps/mobile?

The external contributor pull request merge rate for MerginMaps/mobile is 61.9%, based on public PR activity from non-core contributors.

Are there Good First Issues available in MerginMaps/mobile?

MerginMaps/mobile currently has 7 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".

MerginMaps
MerginMaps/mobileA•Welcoming389
GitHub
Back to Explorer
MerginMaps

MerginMaps/mobile

389
InactiveA•Welcoming(69/100)C++

Mergin Maps mobile app 📲 Open QGIS projects and manage vector data on your phone, even offline 📶 (Android/iOS/Windows app)

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Empathetic Technical Mentor

Warmth Score
8.0/10
Patience Score
8.4/10
Nitpick Rate
25%

Highly welcoming maintainers in MerginMaps/mobile. Prompt code reviews with positive guidance for new contributors.

Top PR Submission Do's

  • •Ensure code complies with the project coding style
  • •Keep PRs scoped to a single concern
  • •Include context and link to the related issue

Top PR Friction Pitfalls (Don'ts)

  • •Do not submit PRs without linking an issue
  • •Do not break existing tests without fixing them
  • •Do not mix unrelated refactors in a single PR
Response Velocity
-
No reviewer activity recorded

Average Response Latency

Tracks hours until a maintainer leaves a review, comment, or PR response.

Merge Efficiency
61.9%
Moderate PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
100.0%
Strong first-timer PR acceptance rate

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
14 core
Highly collaborative maintainer core
Diagnostic Health HUD
61.9%
Merge Gauge
100.0%
1st-Timer
Community Vibe55/100

Embed C-Rank Badge

Show contributors that your repository actively reviews and merges external pull requests.

GetMerged C-Rank badge for MerginMaps/mobile
[![GetMerged C-Rank](https://getmerged.abhishekco.de/api/badge/MerginMaps/mobile)](https://getmerged.abhishekco.de/MerginMaps/mobile?utm_source=github&utm_medium=badge)

Active Good First Issues (5)

View on GitHub

Description When deleting a workspace or account, the user is required to type the account name to confirm deletion. If the user cancels the dialog and reopens it later, the confirmation input field still contains the previously typed name instead of being empty. Environment Staging Application (+ app version, build, operating system) Mergin Maps Mobile App Android: 2026.3.2 / Samsung Galaxy A53 5G, Android 16 iOS: 2026.3.2 / iOS 26.0 Steps to reproduce Open account settings Tap Close account Type the account name in the confirmation input Tap Cancel (do not confirm deletion) Reopen the delete dialog Actual results The confirmation input field still contains the name entered in step 3. Expected results The confirmation input field should be empty each time the delete dialog is opened. Conclusion Created by Claude and supervised by a human test analyst.

📅 Opened Aug 25, 2026💬 0 comments
Quality: 50/100Contribute

Description The delete button on a photo changes colour from rose (salmon pink) to green when tapped, which is inconsistent and misleading. Environment [x] staging Application (+ app version, build, operating system) Dev/OS/app: Samsung Galaxy A53 5G, Android 15 / MM 2026.3.0 - 833251 Dev/OS/app: IPhone 15 / iOS 26 / MM 2026.3.0 - 26.7.927411 Steps to reproduce Open a feature form containing a photo attachment. Tap the delete button on the photo. Observe the button colour change. Actual results The delete button colour changes from rose to green on tap. Expected results The delete button should remain rose (or change to a darker shade of rose/red) on tap Screenshots or logs Screen_Recording_20260715_133625.mp4 Conclusion Created by Claude and supervised by a human test analyst.

📅 Opened Jul 15, 2026💬 7 comments
Quality: 80/100Contribute

Description When entering % or _ into a text filter input in the mobile app, all features are returned instead of treating these characters as literals. Both % and _ are SQL wildcard characters and must be escaped before being used in a filter query — they should match only features whose field value literally contains % or _, not act as wildcards returning everything. Environment [ ] Staging [x] PROD Application (+ app version, build, operating system) Mergin Maps iOS 2026.2.0, iOS 26.0 Steps to reproduce Open project tester-ws-1/preview_mode_bug Navigate to the filter page Open a text filter (e.g. Text-POI-notes) → enter % → apply Reset filter → open the same text filter → enter _ → apply Actual results All features with non empty "notes" field are returned for both % and _ — the characters are interpreted as SQL wildcards (% = any string, _ = any single character). Expected results % and _ should be treated as literal characters. Only features whose field value lite

📅 Opened Jun 1, 2026💬 1 comment
Quality: 30/100Contribute

When a survey form is laid out with a row that has conditional visibility and the row is within a group box, the group box label is duplicated in the mobile app. To reproduce Use the attached project: conditional_rows.zip OR Create a project with the following conditions: A field with either a value map widget or 'True/False' tick box widget A group box with conditional visibility based on a value from the previous field which contains: A second field with either a value map widget or 'True/False' tick box widget A row with conditional visibility based on a value from the previous field Another field within the conditional visibility row A field in the group box that is below but not within the conditional visibility row Once the project is created, or using the example project: Open the project in the mobile app Fill out a feature selecting values so that all of the conditional visibility fields are visible Results In the mobile app, the label of the group box is duplicated whe

📅 Opened May 19, 2026💬 0 comments
Quality: 30/100Contribute

Description When switching between the "Features" and "Layer info" tabs by swiping, the wrong tab is highlighted in the bottom navigation bar — the active page and the highlighted tab do not match. Environment [ ] Staging [x] PROD Application (+ app version, build, operating system) iOS app version: 2026.1.3 iOS version: 26.0 Steps to reproduce Open a project and navigate to a layer's feature list Switch between the Features and Layer info tabs by swiping (not by tapping the tab) Observe the highlighted tab in the bottom navigation bar Actual results The wrong tab is highlighted after swiping — the highlighted tab does not correspond to the currently visible page. Expected results The highlighted tab in the bottom navigation bar should always match the currently visible page, regardless of whether the switch was done by swiping or tapping. Screenshots or logs ScreenRecording_04-23-2026.09-58-54_1.MP4 Conclusion Created by Claude and supervi

📅 Opened Apr 23, 2026💬 0 comments
Quality: 30/100Contribute
Looking for more C++ beginner tasks?Explore C++ GFI

Contributor Community Vibe Feedback

Rate what actually matters after opening a pull request here.

Have you contributed to this repo?

Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.

3 ratings required
Maintainer helpfulness
Review speed
Beginner friendliness

Contributor Compatibility & Review Speed Analysis for MerginMaps/mobile

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 -. Out of all submitted pull requests from non-core authors in the last 180-day window, 61.9% were successfully merged into the primary branch.

Frequently Asked Questions - Contributing to MerginMaps/mobile

01

Is MerginMaps/mobile welcoming to first-time open-source contributors?

MerginMaps/mobile 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.

02

How fast can I expect code review feedback on my pull request?

The initial maintainer response time averages ~-. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 68.6 C-Rank™ score represent?

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 68.6 places MerginMaps/mobile in the Welcoming tier.

04

What is the external contributor pull request merge rate for MerginMaps/mobile?

The external pull request merge rate is 61.9%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.

05

Are there beginner Good First Issues open in MerginMaps/mobile?

Yes, MerginMaps/mobile currently has 7 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.

GetMerged C-Rank™ Indexing Standard

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.