🐚bash/POSIX-compatible shell implemented in Rust 🦀
C-Rank Grade: A (Welcoming) - 70/100
External PR Merge Rate: 63%
Response Time: 2h
First Timer Success: 33%
reubeno/brush 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 reubeno/brush respond to incoming external pull requests in approximately 2.2 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 69.6 places reubeno/brush in the A tier.
The external contributor pull request merge rate for reubeno/brush is 63.2%, based on public PR activity from non-core contributors.
reubeno/brush currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Active Rust repository in reubeno/brush with ongoing community development and issue triage.
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/reubeno/brush?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 05:00 to 09:00 UTC (05:00 - 09:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (79% approval). Large PRs (>500 lines) take ~11 hours (28% approval). Keep your diff compact for rapid review.
brush version sh -c -- fix debug build bash version (for comparison) 5.3.0 Platform / OS Linux Steps to reproduce brush -c "some-command &" - does not run at all Actual behavior (brush) When trying to run a command with -c that has an & symbol at the end, the command doesn't run. If there's another command after it, it does run, but the commands run in a seemingly random order, sometimes some of them don't run at all. [~] sh -c "echo 1" 1 [~] sh -c "echo 1 &" # no output :( [~] sh -c "echo 1 & echo 2 & echo 3 & echo 4" 1 2 3 4 [~] sh -c "echo 1 & echo 2 & echo 3 & echo 4" 4 [~] sh -c "echo 1 & echo 2 & echo 3 & echo 4" 4 1 2 [~] sh -c "echo 1 & echo 2 & echo 3 & echo 4" 1 4 [~] sh -c "echo 1 & echo 2 & echo 3 & echo 4" 4 2 1 [~] sh -c "echo 1 & echo 2 & echo 3 & echo 4" 4 1 2 Note that in an interactive shell both running a single command and multiple commands works fine. From my understanding, the fact that they're in random order is expected, but the fact that sometimes only some of
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 reubeno/brush, 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 reubeno/brush acknowledge new external contributions in approximately 2 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 63.2% were successfully merged into the primary branch.
reubeno/brush 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 ~2 hours. 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 69.6 places reubeno/brush in the Welcoming tier.
The external pull request merge rate is 63.2%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, reubeno/brush 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 reubeno/brush 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.