fanmingming/live - Open Source PR Review Scorecard

✯ 可直连访问的电视/广播图标库与相关工具项目 ✯ 🔕 永久免费 直连访问 完整开源 不断完善的台标 支持IPv4/IPv6双栈访问 🔕

C-Rank Grade: D (Risky) - 20/100

External PR Merge Rate: -

Response Time: 11d

First Timer Success: -

Frequently Asked Questions

Is fanmingming/live welcoming to first-time open-source contributors?

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

What does the 20.4 C-Rank™ score (D 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 20.4 places fanmingming/live in the D tier.

What is the external contributor pull request merge rate for fanmingming/live?

The external contributor pull request merge rate for fanmingming/live is 0.0%, based on public PR activity from non-core contributors.

Are there Good First Issues available in fanmingming/live?

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

fanmingming
fanmingming/liveDRisky28.4k
GitHub
Back to Explorer
fanmingming

fanmingming/live

28,391
DRisky(20/100)JavaScript

✯ 可直连访问的电视/广播图标库与相关工具项目 ✯ 🔕 永久免费 直连访问 完整开源 不断完善的台标 支持IPv4/IPv6双栈访问 🔕

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%

Established JavaScript ecosystem in fanmingming/live. Maintains structured code review standards for external contributors.

Top PR Submission Do's

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

Average Response Latency

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

Merge Efficiency
0.0%
Selective PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
0.0%
No first-timer merges recorded in window

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
2 core
Small core review team
Diagnostic Health HUD
0.0%
Merge Gauge
0.0%
1st-Timer
Community Vibe0/100

Embed C-Rank Badge

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

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

Active Good First Issues (0)

View on GitHub

No cached good first issues currently tracked for fanmingming/live.

View all good first issues directly on GitHub

Looking for more JavaScript beginner tasks?Explore JavaScript 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 fanmingming/live

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

Frequently Asked Questions - Contributing to fanmingming/live

01

Is fanmingming/live welcoming to first-time open-source contributors?

fanmingming/live has a recorded first-timer success rate of 0.0%. Repositories ranked Risky 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 ~10 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 20.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 20.4 places fanmingming/live in the Risky tier.

04

What is the external contributor pull request merge rate for fanmingming/live?

The external pull request merge rate is 0.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 fanmingming/live?

fanmingming/live 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 fanmingming/live 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.