Burning through your subscriptions too fast? Paying for stuff you never use? Stop guessing. OpenUsage is free and open source.
C-Rank Grade: A (Welcoming) - 62/100
External PR Merge Rate: 65%
Response Time: -
First Timer Success: 33%
robinebers/openusage 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 robinebers/openusage 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 61.8 places robinebers/openusage in the A tier.
The external contributor pull request merge rate for robinebers/openusage is 65.4%, based on public PR activity from non-core contributors.
robinebers/openusage does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
Balanced & professional review environment in robinebers/openusage. Maintains strict focus on technical quality and test standards.
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/robinebers/openusage?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 03:00 to 07:00 UTC (03:00 - 07:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (82% approval). Large PRs (>500 lines) take ~115 hours (29% approval). Keep your diff compact for rapid review.
Priority High — new users land in a capable menu-bar app with no explanation of what they're looking at or what to do next. Problem OpenUsage today assumes familiarity: First launch seeds default metrics and menu bar pins (DefaultLayout) but never explains what the popover is, how providers are detected, or how to customize the tray. Discovery is accidental: footer Customize/Settings buttons, right-click pin menus, meter-style toggles, reset-time formats, etc. Tooltips exist only in a few places (.help() on refresh, shortcuts, pin denial, pace/meter flip hints) — most core concepts have no in-app guidance. macOS 26 / SwiftUI now offers richer tooltip and tip surfaces (including TipKit and improved .help affordances). We should evaluate what's available and design an onboarding layer that fits a small popover app — not a modal-heavy enterprise tour. Goals Understand the platform options — what TipKit, SwiftUI tips, and macOS 26 tooltip APIs can do in a menu-bar popover contex
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 robinebers/openusage, 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 robinebers/openusage acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 65.4% were successfully merged into the primary branch.
robinebers/openusage 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 61.8 places robinebers/openusage in the Welcoming tier.
The external pull request merge rate is 65.4%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
robinebers/openusage does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.
All metrics displayed for robinebers/openusage 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.