Glances an Eye on your system. A top/htop alternative for GNU/Linux, BSD, macOS and Windows operating systems.
C-Rank Grade: B (Solid) - 53/100
External PR Merge Rate: 57%
Response Time: 2d
First Timer Success: 44%
nicolargo/glances has a recorded first-timer success rate of 44.4%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in nicolargo/glances respond to incoming external pull requests in approximately 51.1 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 53.4 places nicolargo/glances in the B tier.
The external contributor pull request merge rate for nicolargo/glances is 57.4%, based on public PR activity from non-core contributors.
nicolargo/glances currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Balanced & professional review environment in nicolargo/glances. 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/nicolargo/glances?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 07:00 UTC (07: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 ~33 hours (72% approval). Large PRs (>500 lines) take ~245 hours (26% approval). Keep your diff compact for rapid review.
Is your feature request related to a problem? Please describe. Newer releases of Ubuntu and Debian do no longer include hddtemp as that tool is long dead upstream. Similar data can be obtained via smartctl or other more modern solutions. As hddtemp does no longer work on my system, drive temperatures are now gone from Glances, which makes me sad. Describe the solution you'd like Write a drive temp plugin that utilizes smartctl or sensors to obtain drive temperatures (ideally compatible with external drives, too). Describe alternatives you've considered Manually frickle together a working hddtemp solution, which is not a good solution. Additional context n/a
❯ ~/tmp/venv-codegraphcontext/.venv/bin/cgc analyze complexity --threshold 15 No configuration file found. Using defaults. Using database: FalkorDB Initializing services and database connection... Services initialized. Most Complex Functions (threshold: 15): ╭─────────────────────────┬────────────┬─────────────────────────────────────────────────────────────────────────────╮ │ Function │ Complexity │ Location │ ├─────────────────────────┼────────────┼─────────────────────────────────────────────
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 nicolargo/glances, 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 nicolargo/glances acknowledge new external contributions in approximately 2 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 57.4% were successfully merged into the primary branch.
nicolargo/glances has a recorded first-timer success rate of 44.4%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~2 days+. 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 53.4 places nicolargo/glances in the Solid tier.
The external pull request merge rate is 57.4%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, nicolargo/glances 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 nicolargo/glances 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.