Quick, small, performant, multi-platform Discord overlay alternative, for every client
C-Rank Grade: B (Solid) - 56/100
External PR Merge Rate: 67%
Response Time: 5h
First Timer Success: 50%
SpikeHD/Orbolay has a recorded first-timer success rate of 50.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in SpikeHD/Orbolay respond to incoming external pull requests in approximately 5.4 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 56.2 places SpikeHD/Orbolay in the B tier.
The external contributor pull request merge rate for SpikeHD/Orbolay is 66.7%, based on public PR activity from non-core contributors.
SpikeHD/Orbolay currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in SpikeHD/Orbolay. Reviews community pull requests with focus on project quality.
Discussions in SpikeHD/Orbolay 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/SpikeHD/Orbolay?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 05:00 UTC (05:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 02:00 to 06:00 UTC (02:00 - 06:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (83% approval). Large PRs (>500 lines) take ~26 hours (30% approval). Keep your diff compact for rapid review.
Issue Checklist [x ] I have searched for my issue already [x ] I have read the README, including the Compatibility section Describe the bug Launching Orbolay on Gnome results in VRR being broken. Steps To Reproduce Launch game (without Orbolay), set monitor fps on and watch how it fluctuates (VRR = working) Launch Orbolay and return to the game. The FPS is steady on montior refresh (144) and doesn't fluctuates (VRR = off). Close Orbolay and return to game. The FPS fluctuates again. System Info: OS Version: Arch - Gnome 50.4 Orbolay Version: 3.6.0 Any other relevant info: Running on xwayland as the wayland option doesn't work on Gnome. Additional context/Screenshots No additional context except that his is a great and only working app on Gnome. Good work!
Issue Checklist I have searched for my issue already I have read the README, including the Compatibility section Why should this be included? On windows, the Native Discord Overlay injects itself within any app detected, or manually registered as a game. Allowing for the Overlay to stay perfectly within the bounds of the application window. On Linux, no such overlay exists. Orbolay is currently the closest thing to this that I have. And this would bridge one of few more gaps I (and I would guess some others) are really missing from gaming on linux. What (if any) solution do you have in mind? Application such as mangohud are already capable of rendering exclusively inside the game window without much editing needed to the actual launch argument, See this visual example of me starting minecraft with mangohud as the wrapper command: Video hosted on Streamable.com (expires in 2 days after posting) I mention this, to both show that it is entirely possible, and to suggest potentially loo
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 SpikeHD/Orbolay, 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 SpikeHD/Orbolay acknowledge new external contributions in approximately 5 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 66.7% were successfully merged into the primary branch.
SpikeHD/Orbolay has a recorded first-timer success rate of 50.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~5 hours. 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 56.2 places SpikeHD/Orbolay in the Solid tier.
The external pull request merge rate is 66.7%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, SpikeHD/Orbolay 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 SpikeHD/Orbolay 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.