YLabs-FPV/YMapper - Open Source PR Review Scorecard

A cross-platform tool to create automatic Survey/Photogrammetry missions for Drones using DJI Fly/Litchi

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

External PR Merge Rate: 75%

Response Time: 6d

First Timer Success: 100%

Frequently Asked Questions

Is YLabs-FPV/YMapper welcoming to first-time open-source contributors?

YLabs-FPV/YMapper 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 YLabs-FPV/YMapper respond to incoming external pull requests in approximately 149.5 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 42.1 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 42.1 places YLabs-FPV/YMapper in the B tier.

What is the external contributor pull request merge rate for YLabs-FPV/YMapper?

The external contributor pull request merge rate for YLabs-FPV/YMapper is 75.0%, based on public PR activity from non-core contributors.

Are there Good First Issues available in YLabs-FPV/YMapper?

YLabs-FPV/YMapper does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.

YLabs-FPV
YLabs-FPV/YMapperBSolid154
GitHub
Back to Explorer
YLabs-FPV

YLabs-FPV/YMapper

154
BSolid(42/100)Dart

A cross-platform tool to create automatic Survey/Photogrammetry missions for Drones using DJI Fly/Litchi

Compare
Jump to:

AI Maintainer Review Guidelines

Review Persona

Active Open-Source Maintainer

Warmth Score
7.8/10
Patience Score
8.2/10
Nitpick Rate
20%

Growing Dart project in YLabs-FPV/YMapper welcoming community pull requests and bug fixes.

Top PR Submission Do's

  • Ensure code complies with Dart style conventions
  • Keep PRs scoped and well-documented

Top PR Friction Pitfalls (Don'ts)

  • Do not submit unlinked PRs without context
  • Do not break existing automated test suites
Response Velocity
6 days+
Standard maintainer review cycle

Average Response Latency

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

Merge Efficiency
75.0%
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
CRITICAL BUS FACTOR
Single maintainer
No active GitHub maintainers found (may review internally on Gerrit or internal tools)
Diagnostic Health HUD
75.0%
Merge Gauge
100.0%
1st-Timer
Community Vibe60/100

Embed C-Rank Badge

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

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

Active Good First Issues (0)

View on GitHub

No cached good first issues currently tracked for YLabs-FPV/YMapper.

View all good first issues directly on GitHub

Looking for more Dart beginner tasks?Explore Dart 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 YLabs-FPV/YMapper

When evaluating whether to contribute to YLabs-FPV/YMapper, 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 YLabs-FPV/YMapper acknowledge new external contributions in approximately 6 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 75.0% were successfully merged into the primary branch.

Frequently Asked Questions - Contributing to YLabs-FPV/YMapper

01

Is YLabs-FPV/YMapper welcoming to first-time open-source contributors?

YLabs-FPV/YMapper 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 ~6 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 42.1 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 42.1 places YLabs-FPV/YMapper in the Solid tier.

04

What is the external contributor pull request merge rate for YLabs-FPV/YMapper?

The external pull request merge rate is 75.0%. 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 YLabs-FPV/YMapper?

YLabs-FPV/YMapper 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 YLabs-FPV/YMapper 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.