Connect any AI agent to your team in Slack, Teams & Discord. Open-source and self-hostable.
C-Rank Grade: A (Welcoming) - 58/100
External PR Merge Rate: 8%
Response Time: -
First Timer Success: -
sandbox-quantum/switch has a recorded first-timer success rate of 0.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in sandbox-quantum/switch 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.
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.5 places sandbox-quantum/switch in the A tier.
The external contributor pull request merge rate for sandbox-quantum/switch is 8.1%, based on public PR activity from non-core contributors.
sandbox-quantum/switch currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Strict review standards in sandbox-quantum/switch. Ensure PR scope matches issue requirements closely before requesting review.
Discussions in sandbox-quantum/switch 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/sandbox-quantum/switch?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 09:00 UTC (09:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 12:00 to 16:00 UTC (12:00 - 16:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (10% approval). Large PRs (>500 lines) take ~115 hours (15% approval). Keep your diff compact for rapid review.
Summary When a session's tmux target dies, the sidecar retries injection into the dead target indefinitely and never reaps it. Observed 17,425 consecutive failed injections into a dead tmux target recorded in state.json. The agent is unreachable throughout, while the room shows it live — the sidecar's own heartbeat keeps presence green, because presence reflects the sidecar rather than a session. Related to #320 (a different silent-delivery failure), but independent and arguably more damaging. Behaviour observed A session's tmux target is killed (in our case deliberately, to test restart survivability). The sidecar restores that same session id from state.json and begins injecting into the now-dead target. Every injection fails. Nothing reaps the stale entry, and no new session is auto-started. No error surfaces in the room. The agent shows live, last_seen_at stays current, and list_participants reports it as present. Addressed messages receive no reply and no 👀 reaction. Why it
Summary An agent connects, appears live in the room, and can read_context — but never receives an addressed message. There is no error anywhere. Seen on switch-connector 0.9.10. Impact Indistinguishable from a healthy but slow agent. Every observable signal says the agent is fine: the process is up, the MCP server is registered, the package resolves, the room shows the agent present. Only delivery is missing. This is reproducible from a clean install — the npx line below is what the plugin ships, so anyone running the stock connector on a remote host hits it. It is not a one-off environment problem. Root cause hooks/switch_hook.py:333 resolves the channel port from the hook's own parent pid: return os.path.join( os.path.expanduser("~"), ".switch", "sessions", str(os.getppid()), "port" ) That is correct only if the runtime is a direct child of Claude Code. The comment above it says so, and even warns about the mirror case (a hook wrapped in a shell). But .mcp.json at HEAD wraps
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 sandbox-quantum/switch, 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 sandbox-quantum/switch acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 8.1% were successfully merged into the primary branch.
sandbox-quantum/switch has a recorded first-timer success rate of 0.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~-. 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 57.5 places sandbox-quantum/switch in the Welcoming tier.
The external pull request merge rate is 8.1%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, sandbox-quantum/switch 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 sandbox-quantum/switch 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.