l7mp/stunner - Open Source PR Review Scorecard

A Kubernetes media gateway for WebRTC. Contact: [email protected]

C-Rank Grade: C (Moderate) - 35/100

External PR Merge Rate: 44%

Response Time: 3d

First Timer Success: 33%

Frequently Asked Questions

Is l7mp/stunner welcoming to first-time open-source contributors?

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

What does the 35.2 C-Rank™ score (C 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 35.2 places l7mp/stunner in the C tier.

What is the external contributor pull request merge rate for l7mp/stunner?

The external contributor pull request merge rate for l7mp/stunner is 44.4%, based on public PR activity from non-core contributors.

Are there Good First Issues available in l7mp/stunner?

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

l7mp
l7mp/stunnerCModerate1.0k
GitHub
Back to Explorer
l7mp

l7mp/stunner

1,043
CModerate(35/100)Go

A Kubernetes media gateway for WebRTC. Contact: [email protected]

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 Go repository in l7mp/stunner with ongoing community development and issue triage.

Top PR Submission Do's

  • Ensure code complies with Go 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
3 days+
Standard maintainer review cycle

Average Response Latency

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

Merge Efficiency
44.4%
Moderate PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
33.3%
Accepts new contributor PRs

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
1 core
Single maintainer review bottleneck
Diagnostic Health HUD
44.4%
Merge Gauge
33.3%
1st-Timer
Community Vibe28/100

Embed C-Rank Badge

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

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

Active Good First Issues (0)

View on GitHub

No cached good first issues currently tracked for l7mp/stunner.

View all good first issues directly on GitHub

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 l7mp/stunner

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

Frequently Asked Questions - Contributing to l7mp/stunner

01

Is l7mp/stunner welcoming to first-time open-source contributors?

l7mp/stunner has a recorded first-timer success rate of 33.3%. Repositories ranked Moderate 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 ~3 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 35.2 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 35.2 places l7mp/stunner in the Moderate tier.

04

What is the external contributor pull request merge rate for l7mp/stunner?

The external pull request merge rate is 44.4%. 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 l7mp/stunner?

l7mp/stunner 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 l7mp/stunner 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.