albar965/littlenavmap - Open Source PR Review Scorecard

Little Navmap is a free flight planner, navigation tool, moving map, airport search and airport information system for Flight Simulator X, Microsoft Flight Simulator 2020, Prepar3D and X-Plane.

C-Rank Grade: B (Solid) - 49/100

External PR Merge Rate: 67%

Response Time: 1h

First Timer Success: 100%

Frequently Asked Questions

Is albar965/littlenavmap welcoming to first-time open-source contributors?

albar965/littlenavmap has a recorded first-timer success rate of 100.0%. Repositories ranked B 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 albar965/littlenavmap respond to incoming external pull requests in approximately 1.4 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 49.4 C-Rank™ score (B 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 49.4 places albar965/littlenavmap in the B tier.

What is the external contributor pull request merge rate for albar965/littlenavmap?

The external contributor pull request merge rate for albar965/littlenavmap is 66.7%, based on public PR activity from non-core contributors.

Are there Good First Issues available in albar965/littlenavmap?

albar965/littlenavmap does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.

albar965
albar965/littlenavmapBSolid1.6k
GitHub
Back to Explorer
albar965

albar965/littlenavmap

1,596
BSolid(49/100)C++

Little Navmap is a free flight planner, navigation tool, moving map, airport search and airport information system for Flight Simulator X, Microsoft Flight Simulator 2020, Prepar3D and X-Plane.

Compare
Jump to:
Response Velocity
1 hours
Standard maintainer review cycle

Average Response Latency

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

Merge Efficiency
66.7%
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
2 core
Small core review team
Diagnostic Health HUD
66.7%
Merge Gauge
100.0%
1st-Timer
Community Vibe86/100

Embed C-Rank Badge

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

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

Active Good First Issues (0)

View on GitHub

No cached good first issues currently tracked for albar965/littlenavmap.

View all good first issues directly on GitHub

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 albar965/littlenavmap

When evaluating whether to contribute to albar965/littlenavmap, 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 albar965/littlenavmap acknowledge new external contributions in approximately 1 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 66.7% were successfully merged into the primary branch.

Frequently Asked Questions - Contributing to albar965/littlenavmap

01

Is albar965/littlenavmap welcoming to first-time open-source contributors?

albar965/littlenavmap has a recorded first-timer success rate of 100.0%. Repositories ranked Solid 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 ~1 hours. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 49.4 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 49.4 places albar965/littlenavmap in the Solid tier.

04

What is the external contributor pull request merge rate for albar965/littlenavmap?

The external pull request merge rate is 66.7%. 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 albar965/littlenavmap?

albar965/littlenavmap does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.

GetMerged C-Rank™ Indexing Standard

All metrics displayed for albar965/littlenavmap 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.