aviator-co/av - Open Source PR Review Scorecard

A command line tool to manage stacked PRs with Aviator

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

External PR Merge Rate: 67%

Response Time: 2d

First Timer Success: 100%

Frequently Asked Questions

Is aviator-co/av welcoming to first-time open-source contributors?

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

What does the 49.9 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.9 places aviator-co/av in the B tier.

What is the external contributor pull request merge rate for aviator-co/av?

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

Are there Good First Issues available in aviator-co/av?

aviator-co/av currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".

aviator-co
aviator-co/avBSolid509
GitHub
Back to Explorer
aviator-co

aviator-co/av

509
BSolid(50/100)Go

A command line tool to manage stacked PRs with Aviator

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%

Active maintainer team in aviator-co/av welcoming community pull requests and bug fixes.

Top PR Submission Do's

  • Ensure code complies with repository style conventions
  • Keep PRs focused 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
1 days+
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 Vibe57/100

Embed C-Rank Badge

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

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

Active Good First Issues (1)

View on GitHub

If you have a branch checked out on a worktree, and that branch has been merged, we attempt to delete the branch and fail with the error: error: cannot delete merged branch "more_ci_improvements": git branch: exit status 1 ❯ git switch more_ci_improvements fatal: 'more_ci_improvements' is already used by worktree at '/worktrees/pr-feedback' We should provide a better error message to the user to explain the cause and potentially give advice on how they can recover from this situation. We should also avoid leaving the user in a detached head state when av sync fails to delete a branch

📅 Opened Jan 29, 2026💬 0 comments
Quality: 30/100Contribute
Looking for more Go beginner tasks?Explore Go 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 aviator-co/av

When evaluating whether to contribute to aviator-co/av, 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 aviator-co/av acknowledge new external contributions in approximately 1 days+. 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 aviator-co/av

01

Is aviator-co/av welcoming to first-time open-source contributors?

aviator-co/av 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 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 49.9 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.9 places aviator-co/av in the Solid tier.

04

What is the external contributor pull request merge rate for aviator-co/av?

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 aviator-co/av?

Yes, aviator-co/av currently has 1 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 aviator-co/av 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.