A Dynamic Island-style command center for managing all your AI coding agents on macOS.
C-Rank Grade: A (Welcoming) - 65/100
External PR Merge Rate: 74%
Response Time: -
First Timer Success: 57%
erha19/ping-island has a recorded first-timer success rate of 57.1%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in erha19/ping-island 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 65.5 places erha19/ping-island in the A tier.
The external contributor pull request merge rate for erha19/ping-island is 74.4%, based on public PR activity from non-core contributors.
erha19/ping-island currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Responsive & active maintainer team in erha19/ping-island. Reviews pull requests with focus on project architectural goals.
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/erha19/ping-island?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 08:00 UTC (08:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 06:00 to 10:00 UTC (06:00 - 10:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (93% approval). Large PRs (>500 lines) take ~115 hours (34% approval). Keep your diff compact for rapid review.
Context from this repo: #88 was "remote-agent-service dies silently after the Mac sleeps" - the SSH tunnel drops, the remote service writes to a dead socket, SIGPIPE. That was fixed as a reconnect bug, but the trigger was the machine sleeping while an agent was still working. Ping Island already tracks the state needed to prevent the trigger itself. Proposal: hold IOPMAssertionCreateWithName / kIOPMAssertPreventUserIdleSystemSleep while any tracked session is in a working state; release when all sessions are idle or waiting-for-input. The power API is trivial. The hard part - knowing when an agent is genuinely working rather than just having a live process - is what Ping Island already solves. Survey: I checked 11 agent-monitoring and transcript tools (MioIsland, agentbro, claude-monitor, claude-code-monitor, claude-code-log, langfuse template, and others). None do power management. The keep-awake tools that exist (caffeinate wrappers, PowerToys Awake, agents-sleep-preventer) are the i
Good software! But when I tried to use ping-island on Linux servers, it will first create many coding agent directories in my home directory, e.g. .codex, .qoder, .openclaw, even though I only use one coding agent (Claude). Is it possible to only create directories that are necessary?
希望支持的客户端 CodeWhale — 一款开源（MIT）终端编程智能体，专为 DeepSeek V4 打造，架构与 Claude Code 高度兼容。目前 38k + star，用户群快速增长。 为什么需要 CodeWhale 在架构上和 Claude Code 同源：同样的 tool-calling 协议、同样的 hook 事件模型、同样的 session 生命周期。很多用户（包括我）同时跑 Claude Code 和 CodeWhale，希望能通过 Ping Island 的统一面板监控 CodeWhale 的会话状态。
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 erha19/ping-island, 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 erha19/ping-island acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 74.4% were successfully merged into the primary branch.
erha19/ping-island has a recorded first-timer success rate of 57.1%. 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 65.5 places erha19/ping-island in the Welcoming tier.
The external pull request merge rate is 74.4%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, erha19/ping-island 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 erha19/ping-island 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.