A stable, powerful and updated wrapper around Lavalink
C-Rank Grade: D (Risky) - 14/100
External PR Merge Rate: -
Response Time: 6d
First Timer Success: -
shipgirlproject/Shoukaku 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.
Maintainers in shipgirlproject/Shoukaku respond to incoming external pull requests in approximately 146.8 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 14.1 places shipgirlproject/Shoukaku in the D tier.
The external contributor pull request merge rate for shipgirlproject/Shoukaku is 0.0%, based on public PR activity from non-core contributors.
shipgirlproject/Shoukaku currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
A stable, powerful and updated wrapper around Lavalink
Collaborative maintainer environment in shipgirlproject/Shoukaku. Reviews community pull requests with focus on project quality.
Discussions in shipgirlproject/Shoukaku 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/shipgirlproject/Shoukaku?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
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~95 hours (81% approval). Large PRs (>500 lines) take ~705 hours (29% approval). Keep your diff compact for rapid review.
Before v5 todo: #244 - tooling changes #225 (see #185) #227 - mocking LL API remove cached player data, handled in queue anyways (see #229) #232 (see #220) #226 #203 - replaces guide website #190 - breaking Player#move resuming (see #135) correct deviations from LL types code cleanup, reorganization move class property inits to constructor string unions into enums misc example queue / endorse wrapper w/ queue docs v4 to v5 upgrade guide examples misc testing More items may be added in the future, PRs addressing a task will be linked as they are created. Please help test v5 features and provide feedback here.
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 shipgirlproject/Shoukaku, 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 shipgirlproject/Shoukaku acknowledge new external contributions in approximately 6 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.
shipgirlproject/Shoukaku 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.
The initial maintainer response time averages ~6 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 14.1 places shipgirlproject/Shoukaku in the Risky tier.
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.
Yes, shipgirlproject/Shoukaku currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for shipgirlproject/Shoukaku 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.