The open source menu bar manager
C-Rank Grade: A (Welcoming) - 67/100
External PR Merge Rate: 70%
Response Time: -
First Timer Success: 69%
thaw-app/Thaw has a recorded first-timer success rate of 68.8%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in thaw-app/Thaw 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 67.5 places thaw-app/Thaw in the A tier.
The external contributor pull request merge rate for thaw-app/Thaw is 69.7%, based on public PR activity from non-core contributors.
thaw-app/Thaw currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Rigorous architecture standards (63% critical review signals). Ensure PRs strictly follow guidelines before requesting review in thaw-app/Thaw.
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/thaw-app/Thaw?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 03:00 UTC (03:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 00:00 to 04:00 UTC (00:00 - 04:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (87% approval). Large PRs (>500 lines) take ~115 hours (31% approval). Keep your diff compact for rapid review.
Maintainer Status (July 25, 2026) by @diazdesandi Support is in preview, with Preview 5 now available — much less experimental than the early builds. In everyday use, Thaw works well on macOS 27, with a few remaining edge cases. Current state Thaw on macOS 27 is in a “works well for most people, with minor issues left to polish” state. Focus is on stabilization and regression testing. If nothing blocking turns up from Preview 5, the next step is moving macOS 27 support into the Alpha / Nightly phase as part of the v2.1.0 cycle. Original report Pre-submission Checklist I searched existing issues (open & closed) and found no duplicates Problem / Use Case Thaw not working on Golden Gate! Proposed Solution Update Thaw to make it compatible with Golden Gate! Alternatives Considered No response Additional Context No response
Want to help Thaw? This issue lists contribution asks that don't already have their own bug or feature ticket. Read Contributing first. External pull requests should target the development branch. How to help Pick something from Current asks below, or propose another small improvement in a comment. Comment with what you'll take so work doesn't overlap. Keep changes small and focused. Open a PR that references this issue when relevant. Translations Translations are managed on Crowdin. The README Languages section lists the current languages, and Crowdin shows per-language progress. Translation PRs are not accepted in this repo. Current asks Comment on this issue to claim an item. Refresh docs screenshots. UI captures in Frequent Issues and other docs may be outdated. Retake and update them on macOS 26+, and note macOS 27 where relevant. README images are out of scope for this ask. Some assets live as files in the repo or elsewhere; if you're not sure which ones to update or where th
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 thaw-app/Thaw, 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 thaw-app/Thaw acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 69.7% were successfully merged into the primary branch.
thaw-app/Thaw has a recorded first-timer success rate of 68.8%. 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 67.5 places thaw-app/Thaw in the Welcoming tier.
The external pull request merge rate is 69.7%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, thaw-app/Thaw 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 thaw-app/Thaw 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.