Machine learning powered Karaoke app (with scores!)
C-Rank Grade: B (Solid) - 53/100
External PR Merge Rate: 63%
Response Time: 1d
First Timer Success: 75%
rzru/nightingale has a recorded first-timer success rate of 75.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in rzru/nightingale respond to incoming external pull requests in approximately 29.3 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
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 53.3 places rzru/nightingale in the B tier.
The external contributor pull request merge rate for rzru/nightingale is 62.5%, based on public PR activity from non-core contributors.
rzru/nightingale currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Machine learning powered Karaoke app (with scores!)
Collaborative maintainer environment in rzru/nightingale. Reviews community pull requests with focus on project quality.
Discussions in rzru/nightingale focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.
Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/rzru/nightingale?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 00:00 UTC (00:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 08:00 to 12:00 UTC (08:00 - 12:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~19 hours (78% approval). Large PRs (>500 lines) take ~141 hours (28% approval). Keep your diff compact for rapid review.
Currently, the project appears to use two different python packages for stem separation: When the user selects demucs, it calls out to https://pypi.org/project/demucs/ When the user selects UVR (the default), it calls out to https://pypi.org/project/audio-separator/ Both paths could potentially be consolidated to use https://pypi.org/project/uvr-headless-runner/. uvr-headless-runner is set up as a command-line tool, but also provides a convenient python API. Aside from code consolidation, this package has the benefit of supporting GPU acceleration on AMD GPUs via DirectML (when running on Windows).
This happens especially in vocals-heavy segments (f.e, with the rap songs). None of the parameter tweaks I've tried fixed the problem entirely, and I can't figure out what the cause is. Context overflow, perhaps? Would also appreciate some contributions on this matter.
That's a known issue I'm still working to understand. Sometimes, especially when the vocals stem contains back-vocals and/or chorus, the alignment slides off the rails, sometimes it thinks the word is longer than it actually is, and in general, it is pretty non-deterministic. I would appreciate any support from the experienced with the alignment models devs to figure out this issue
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to rzru/nightingale, 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 rzru/nightingale acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 62.5% were successfully merged into the primary branch.
rzru/nightingale has a recorded first-timer success rate of 75.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~1 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
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 53.3 places rzru/nightingale in the Solid tier.
The external pull request merge rate is 62.5%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, rzru/nightingale currently has 3 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for rzru/nightingale 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.