Space Rabbit removes animations when switching macOS Spaces. Reclaim hours of your time every month!
C-Rank Grade: A (Welcoming) - 67/100
External PR Merge Rate: 70%
Response Time: 1h
First Timer Success: 100%
Tahul/space-rabbit 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.
Maintainers in Tahul/space-rabbit respond to incoming external pull requests in approximately 1.0 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 66.9 places Tahul/space-rabbit in the A tier.
The external contributor pull request merge rate for Tahul/space-rabbit is 70.0%, based on public PR activity from non-core contributors.
Tahul/space-rabbit currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in Tahul/space-rabbit. Prompt code reviews with positive guidance for new contributors.
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/Tahul/space-rabbit?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 Tuesday - Thursday from 05:00 to 09:00 UTC (05:00 - 09:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (88% approval). Large PRs (>500 lines) take ~5 hours (32% approval). Keep your diff compact for rapid review.
I can't discern a difference between 'fast' and 'instant', and all of them are too fast for my liking. If not a millisecond value selector, then maybe a 'medium' setting halfway between 'normal' and 'fast'? Thanks for making this.
Instant app switch [cmd+tab] (between spaces) is unreliable [MacOS 27 Version 27.0 Beta (26A5388g)] – sometimes it works instantly, sometimes I see the animation.
Problem The keyboard event tap swallows a matched Space shortcut even when posting the replacement DockSwipe fails. In App/EventTap.swift, the left/right shortcut path calls postSwitchGesture(direction:) and records a switch only when it returns true, but then returns nil unconditionally. If event creation or posting fails, the original shortcut has already been swallowed and macOS never receives a native fallback. Expected behavior If the replacement gesture cannot be created or posted, the original key event should be passed through so macOS can perform its normal Space switch. The expected control flow is: Successful synthetic gesture: record the switch and swallow the original event. Failed synthetic gesture: pass the original event through unchanged. Why this matters This is a fail-closed behavior at the input boundary: a rare allocation or posting failure can turn a recoverable instant-switch failure into a shortcut that appears to do nothing. Suggested fix Return the existing
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 Tahul/space-rabbit, 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 Tahul/space-rabbit acknowledge new external contributions in approximately 1 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 70.0% were successfully merged into the primary branch.
Tahul/space-rabbit 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.
The initial maintainer response time averages ~1 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 66.9 places Tahul/space-rabbit in the Welcoming tier.
The external pull request merge rate is 70.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, Tahul/space-rabbit 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 Tahul/space-rabbit 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.