alexta69/metube - Open Source PR Review Scorecard

Self-hosted video downloader for YouTube and other sites (web UI for yt-dlp)

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

External PR Merge Rate: 56%

Response Time: 10h

First Timer Success: 100%

Frequently Asked Questions

Is alexta69/metube welcoming to first-time open-source contributors?

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

What does the 57.0 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 57.0 places alexta69/metube in the B tier.

What is the external contributor pull request merge rate for alexta69/metube?

The external contributor pull request merge rate for alexta69/metube is 55.6%, based on public PR activity from non-core contributors.

Are there Good First Issues available in alexta69/metube?

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

alexta69
alexta69/metubeB•Solid14.8k
GitHub
Back to Explorer
alexta69

alexta69/metube

14,844
InactiveB•Solid(57/100)Low Sample (<20 PRs)Python

Self-hosted video downloader for YouTube and other sites (web UI for yt-dlp)

GitHub
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 alexta69/metube 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
9 hours
Standard maintainer review cycle

Average Response Latency

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

Merge Efficiency
55.6%
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
4 core
Small core review team
Diagnostic Health HUD
55.6%
Merge Gauge
100.0%
1st-Timer
Community Vibe75/100

Embed C-Rank Badge

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

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

Active Good First Issues (3)

View on GitHub

Consolidates #222, #769, #953, #426 (and the format-listing part of many older requests). The recurring ask: before downloading, probe the URL (extract_info with download=False) and let the user pick — resolution/format with file sizes (#222), audio track/language for multi-audio videos (#953, #769), and toggles like embedding the cover (#426). Design direction (aligned with the playlist Browse modal accepted in #1030): the Download button becomes a split button; a "Browse formats…" action probes the URL and opens a modal listing available formats/tracks (reusing the existing selection framework). The chosen format_ids are submitted as a per-download format override — the backend already supports per-download ytdl_options_overrides. No new persistent state. This is community-contribution territory (see the feature request guidelines). If you want to work on it, comment here first so we can agree on the UI before you invest in a PR. A good first slice would be video formats only,

📅 Opened Jul 18, 2026💬 1 comment
Quality: 80/100Contribute

Given the scope line from #1027 ("MeTube writes the file once, as correctly as it can"), checking before sending a PR this time. The idea: a Browse action next to Download/Subscribe for playlist/channel URLs. It flat-probes the URL (no download) and shows the entries as a list — title, duration, thumbnail — with checkboxes. The user picks items and "Add selected" queues each one as a normal individual download with the form's current settings. Nothing happens to files after they are written; this is purely about choosing what gets downloaded, for the case where you want 7 tracks out of a 400-item playlist and the item-limit slider can't express that. The part I suspect you'll want to weigh: to badge entries as "already downloaded" (and offer a hide-them filter), my draft keeps a small persistent registry of finished source URLs (normalized, so youtu.be/music.youtube/shorts variants match) in STATE_DIR, updated when a download finishes. That's new persistent state, which I know you'

📅 Opened Jul 16, 2026💬 2 comments
Quality: 80/100Contribute

Prerequisites I have searched existing issues and discussions to ensure this feature hasn't been requested before I have read the feature request guidelines in the README I understand that MeTube development relies on community contributions and the maintainer is not likely to implement this feature I have considered if this feature should be implemented in yt-dlp instead of MeTube (if so, please report to yt-dlp repository) Feature Description I have metube monitoring several channels subscriptions. For my use case, I have some set to auto-download, but most go into the queue for manual review before download (or deletion). This mostly works great, but because I have multiple videos pending, some from channels covering similar content, it's hard to quickly identify which video is from which channel, which often feeds into my decision to download or delete. metube provides OUTPUT_TEMPLATE to set the output filename. I set it to "%(channel)s - %(title)s.%(ext)s" to prefix my dow

📅 Opened Jun 3, 2026💬 3 comments
Quality: 45/100Contribute
Looking for more Python beginner tasks?Explore Python 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 alexta69/metube

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

Frequently Asked Questions - Contributing to alexta69/metube

01

Is alexta69/metube welcoming to first-time open-source contributors?

alexta69/metube 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 ~9 hours. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 57.0 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.0 places alexta69/metube in the Solid tier.

04

What is the external contributor pull request merge rate for alexta69/metube?

The external pull request merge rate is 55.6%. 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 alexta69/metube?

Yes, alexta69/metube currently has 3 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 alexta69/metube 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.