euzu/tuliprox - Open Source PR Review Scorecard

Flexible IPTV playlist processor & proxy in Rust 🦀 - supports M3U, Xtream Codes, HDHomeRun, Plex, Emby & Jellyfin. Filtering, merging, scheduling & web delivery.

C-Rank Grade: A (Welcoming) - 57/100

External PR Merge Rate: 69%

Response Time: 4d

First Timer Success: 50%

Frequently Asked Questions

Is euzu/tuliprox welcoming to first-time open-source contributors?

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

What does the 57.2 C-Rank™ score (A 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 57.2 places euzu/tuliprox in the A tier.

What is the external contributor pull request merge rate for euzu/tuliprox?

The external contributor pull request merge rate for euzu/tuliprox is 69.2%, based on public PR activity from non-core contributors.

Are there Good First Issues available in euzu/tuliprox?

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

euzu
euzu/tuliproxA•Welcoming573
GitHub
Back to Explorer
euzu

euzu/tuliprox

573
InactiveA•Welcoming(57/100)Rust

Flexible IPTV playlist processor & proxy in Rust 🦀 - supports M3U, Xtream Codes, HDHomeRun, Plex, Emby & Jellyfin. Filtering, merging, scheduling & web delivery.

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Welcoming Community Builder

Warmth Score
8.5/10
Patience Score
8.6/10
Nitpick Rate
30%

Highly welcoming maintainers in euzu/tuliprox. Prompt code reviews with positive guidance for new contributors.

Top PR Submission Do's

  • •Ensure code complies with the project coding style
  • •Keep PRs scoped to a single concern
  • •Include context and link to the related issue

Top PR Friction Pitfalls (Don'ts)

  • •Do not submit PRs without linking an issue
  • •Do not break existing tests without fixing them
  • •Do not mix unrelated refactors in a single PR
Response Velocity
4 days+
Standard maintainer review cycle

Average Response Latency

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

Merge Efficiency
69.2%
Moderate PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
50.0%
Accepts new contributor PRs

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
12 core
Highly collaborative maintainer core
Diagnostic Health HUD
69.2%
Merge Gauge
50.0%
1st-Timer
Community Vibe43/100

Embed C-Rank Badge

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

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

Active Good First Issues (1)

View on GitHub

I can't figure out how to dynamically assign vod content a genre using tmdb metadata. Could you please provide an example.

📅 Opened Sep 6, 2026💬 2 comments
Quality: 50/100Contribute
Looking for more Rust beginner tasks?Explore Rust 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 euzu/tuliprox

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

Frequently Asked Questions - Contributing to euzu/tuliprox

01

Is euzu/tuliprox welcoming to first-time open-source contributors?

euzu/tuliprox has a recorded first-timer success rate of 50.0%. Repositories ranked Welcoming 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 ~4 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 57.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 57.2 places euzu/tuliprox in the Welcoming tier.

04

What is the external contributor pull request merge rate for euzu/tuliprox?

The external pull request merge rate is 69.2%. 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 euzu/tuliprox?

Yes, euzu/tuliprox 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 euzu/tuliprox 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.