ClementTsang/bottom - Open Source PR Review Scorecard

Yet another cross-platform graphical process/system monitor.

C-Rank Grade: A (Welcoming) - 57/100

External PR Merge Rate: 92%

Response Time: 9d

First Timer Success: 50%

Frequently Asked Questions

Is ClementTsang/bottom welcoming to first-time open-source contributors?

ClementTsang/bottom has a recorded first-timer success rate of 50.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.

How fast can I expect code review feedback on my pull request?

Maintainers in ClementTsang/bottom respond to incoming external pull requests in approximately 222.8 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 56.6 C-Rank™ score (A Tier) represent?

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 56.6 places ClementTsang/bottom in the A tier.

What is the external contributor pull request merge rate for ClementTsang/bottom?

The external contributor pull request merge rate for ClementTsang/bottom is 91.6%, based on public PR activity from non-core contributors.

Are there Good First Issues available in ClementTsang/bottom?

ClementTsang/bottom does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.

ClementTsang
ClementTsang/bottomAWelcoming13.9k
GitHub
Back to Explorer
ClementTsang

ClementTsang/bottom

13,929
AWelcoming(57/100)Rust

Yet another cross-platform graphical process/system monitor.

Compare
Jump to:
Response Velocity
9 days+
Standard maintainer review cycle

Average Response Latency

Tracks hours until a maintainer leaves a review, comment, or PR response.

Merge Efficiency
91.6%
High acceptance rate for external PRs

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
50.0%
Accepts new contributor PRs

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
7 core
Highly collaborative maintainer core
Diagnostic Health HUD
91.6%
Merge Gauge
50.0%
1st-Timer
Community Vibe52/100

Embed C-Rank Badge

Show contributors that your repository actively reviews and merges external pull requests.

GetMerged C-Rank badge for ClementTsang/bottom
[![GetMerged C-Rank](https://getmerged.abhishekco.de/api/badge/ClementTsang/bottom)](https://getmerged.abhishekco.de/ClementTsang/bottom?utm_source=github&utm_medium=badge)

Active Good First Issues (0)

View on GitHub

No cached good first issues currently tracked for ClementTsang/bottom.

View all good first issues directly on GitHub

Looking for more Rust beginner tasks?Explore Rust GFI

Contributor Community Vibe Feedback

Rate what actually matters after opening a pull request here.

Have you contributed to this repo?

Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.

3 ratings required
Maintainer helpfulness
Review speed
Beginner friendliness

Contributor Compatibility & Review Speed Analysis for ClementTsang/bottom

When evaluating whether to contribute to ClementTsang/bottom, 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 ClementTsang/bottom acknowledge new external contributions in approximately 9 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 91.6% were successfully merged into the primary branch.

Frequently Asked Questions - Contributing to ClementTsang/bottom

01

Is ClementTsang/bottom welcoming to first-time open-source contributors?

ClementTsang/bottom has a recorded first-timer success rate of 50.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.

02

How fast can I expect code review feedback on my pull request?

The initial maintainer response time averages ~9 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 56.6 C-Rank™ score represent?

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 56.6 places ClementTsang/bottom in the Welcoming tier.

04

What is the external contributor pull request merge rate for ClementTsang/bottom?

The external pull request merge rate is 91.6%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.

05

Are there beginner Good First Issues open in ClementTsang/bottom?

ClementTsang/bottom does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.

GetMerged C-Rank™ Indexing Standard

All metrics displayed for ClementTsang/bottom 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.