Welcome to a calmer internet
C-Rank Grade: A (Welcoming) - 66/100
External PR Merge Rate: 58%
Response Time: -
First Timer Success: 33%
zen-browser/desktop has a recorded first-timer success rate of 33.3%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in zen-browser/desktop 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 66.5 places zen-browser/desktop in the A tier.
The external contributor pull request merge rate for zen-browser/desktop is 58.0%, based on public PR activity from non-core contributors.
zen-browser/desktop currently has 12 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Rigorous architecture standards (66% critical review signals). Ensure PRs strictly follow guidelines before requesting review in zen-browser/desktop.
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/zen-browser/desktop?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 11:00 UTC (11:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 21:00 to 01:00 UTC (21:00 - 01:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (73% approval). Large PRs (>500 lines) take ~115 hours (26% approval). Keep your diff compact for rapid review.
Preliminary Checks I have read and understood the important section above. I have searched existing issues and avoided creating duplicates. I am not filing an enhancement request. I have checked that this issue cannot be reproduced on Mozilla Firefox. I have checked that this issue can be reproduced once I removed all my Mods and Custom CSS. What happened? In macOS, when not in full screen mode, the traffic lights don't light up and you can't interact with them. Expected behavior traffic lights show their colours on hover and do their functionality on click Actual behavior nothing happens Steps to reproduce for me, this just the perpetual state atm, I haven't found a way for it to not reproduce. Maybe someone else on macOS can share if it's different for them Screenshots and videos Screen.Recording.2026-10-08.at.12.34.17.mov Version 1.23.1b (64-bit) What platform are you seeing the problem on? macOS - aarch64 What component is this issue rela
Preliminary Checks I have read and understood the important section above. I have searched existing issues and avoided creating duplicates. I am not filing an enhancement request. I have checked that this issue cannot be reproduced on Mozilla Firefox. I have checked that this issue can be reproduced once I removed all my Mods and Custom CSS. What happened? zen_aawqZtgmlD.mp4 Expected behavior Tabs on right should have same behaviour as tabs on left. Actual behavior Sidebar theme shifts Steps to reproduce Enable a gradient theme and enable tabs on right. Enable compact mode and hover Screenshots and videos No response Version 1.23b What platform are you seeing the problem on? Windows - x64 What component is this issue related to? Tabs Relevant log output if applicable
Preliminary Checks I have read and understood the important section above. I have searched existing issues and avoided creating duplicates. I am not filing an enhancement request. I have checked that this issue cannot be reproduced on Mozilla Firefox. I have checked that this issue can be reproduced once I removed all my Mods and Custom CSS. What happened? There are multiple accesskey (accelerator key) collisions in the Turkish translation (tr) for bookmark and browser context menus. When right-clicking on items, pressing specific shortcut letters cycles through multiple menu options instead of executing the targeted action immediately. In the bookmark context menu, several items share the exact same access keys: Y key collision: Yeni sekmede aç Yer imleri araç çubuğu i / I key collision: Yeni kapsayıcı sekmede aç Yeni pencerede aç Expected behavior Pressing an accesskey (e.g., 'Y' or 'i') in the context menu should immediately execute the corresponding menu co
Preliminary Checks I have read and understood the important section above. I have searched existing issues and avoided creating duplicates. I am not filing an enhancement request. I have checked that this issue cannot be reproduced on Mozilla Firefox. I have checked that this issue can be reproduced once I removed all my Mods and Custom CSS. What happened? After updating to 1.22.2b, the bottom parts of the lowercase letters g, p, q, and y are clipped in the Application Menu, as well as in the menus opened from the History and Bookmarks buttons. I downgraded to 1.22.1b and confirmed that the letters are displayed normally there. This appears to be a regression introduced in 1.22.2b. Expected behavior The full letters should be displayed normally without any part of them being clipped. Actual behavior The bottom parts of g, p, q, and y are partially cut off. Steps to reproduce Update Zen Browser to 1.22.2b. Open the Application Menu, or click the History or Bookmarks button to op
Preliminary Checks I have read and understood the important section above. I have searched existing issues and avoided creating duplicates. I am not filing an enhancement request. I have checked that this issue cannot be reproduced on Mozilla Firefox. I have checked that this issue can be reproduced once I removed all my Mods and Custom CSS. What happened? tab preview image (or thumbnail) has a larger border radius than its container, which adds black empty spaces in the corners of the container Expected behavior thumbnail has the same border radius as its container Actual behavior thumbnail has the larger border radius than its container Steps to reproduce make sure that browser.tabs.hoverPreview.enabled is true open at least two tabs hover over inactive, but loaded tab to see a thumbnail observe thumbnail Screenshots and videos Version 1.22b What platform are you seeing the problem on? Windows - x64 What component is this issue related to? Tabs Relevant log output if applic
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 zen-browser/desktop, 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 zen-browser/desktop acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 58.0% were successfully merged into the primary branch.
zen-browser/desktop has a recorded first-timer success rate of 33.3%. 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 66.5 places zen-browser/desktop in the Welcoming tier.
The external pull request merge rate is 58.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, zen-browser/desktop currently has 12 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for zen-browser/desktop 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.