GeiserX/whisper-subs - Open Source PR Review Scorecard

Jellyfin plugin for local AI-powered subtitle generation using Whisper - all processing stays on your server

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

External PR Merge Rate: 91%

Response Time: -

First Timer Success: 100%

Frequently Asked Questions

Is GeiserX/whisper-subs welcoming to first-time open-source contributors?

GeiserX/whisper-subs has a recorded first-timer success rate of 100.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 GeiserX/whisper-subs respond to incoming external pull requests in approximately 0.0 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 57.4 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.4 places GeiserX/whisper-subs in the A tier.

What is the external contributor pull request merge rate for GeiserX/whisper-subs?

The external contributor pull request merge rate for GeiserX/whisper-subs is 90.9%, based on public PR activity from non-core contributors.

Are there Good First Issues available in GeiserX/whisper-subs?

GeiserX/whisper-subs does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.

GeiserX
GeiserX/whisper-subsA•Welcoming108
GitHub
Back to Explorer
GeiserX

GeiserX/whisper-subs

108
Active (30d)A•Welcoming(57/100)C#

Jellyfin plugin for local AI-powered subtitle generation using Whisper - all processing stays on your server

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Welcoming Community Builder

Warmth Score
7.9/10
Patience Score
8.2/10
Nitpick Rate
40%

Collaborative maintainer environment in GeiserX/whisper-subs. Reviews community pull requests with focus on project quality.

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
-
No reviewer activity recorded

Average Response Latency

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

Merge Efficiency
90.9%
High acceptance rate for external PRs

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
1 core
Single maintainer review bottleneck
Diagnostic Health HUD
90.9%
Merge Gauge
100.0%
1st-Timer
Community Vibe66/100

Embed C-Rank Badge

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

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

Active Good First Issues (1)

View on GitHub

Problem In forced-subtitle mode (SubtitleMode.ForcedOnly / SubtitleMode.FullAndForced), SubtitleManager splits audio into ~30s VAD-based chunks and calls DetectLanguageAsync once per chunk. Each call spawns a fresh whisper-cli process that must: Load the ~3 GB model from disk Initialize the inference backend (Vulkan shader compilation or CUDA context) Run a trivial language detection pass Exit For a 2-hour movie with ~240 chunks, this means ~240 cold-start process launches. The model-load and backend-init overhead dominates: benchmarks show ~21s/chunk with GPU vs ~15s/chunk CPU-only, because GPU initialization is the bottleneck, not compute. Current mitigation As of e966046, DetectLanguageAsync passes --no-gpu to avoid the worst of the GPU init overhead. This cuts per-chunk time from ~21s to ~15s but doesn't address the fundamental issue: per-chunk process spawning with cold model loads. Proposed long-term fix Move to a persistent whisper-server process that stays loaded between requ

📅 Opened Apr 6, 2026💬 0 comments
Quality: 70/100Contribute
Looking for more C# beginner tasks?Explore C# 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 GeiserX/whisper-subs

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

Frequently Asked Questions - Contributing to GeiserX/whisper-subs

01

Is GeiserX/whisper-subs welcoming to first-time open-source contributors?

GeiserX/whisper-subs has a recorded first-timer success rate of 100.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 ~-. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 57.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 57.4 places GeiserX/whisper-subs in the Welcoming tier.

04

What is the external contributor pull request merge rate for GeiserX/whisper-subs?

The external pull request merge rate is 90.9%. 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 GeiserX/whisper-subs?

GeiserX/whisper-subs 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 GeiserX/whisper-subs 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.