webstonehq/tuxedo - Open Source PR Review Scorecard

A fast, keyboard-driven terminal UI for todo.txt.

C-Rank Grade: B (Solid) - 46/100

External PR Merge Rate: 42%

Response Time: 8h

First Timer Success: 67%

Frequently Asked Questions

Is webstonehq/tuxedo welcoming to first-time open-source contributors?

webstonehq/tuxedo has a recorded first-timer success rate of 66.7%. Repositories ranked B 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 webstonehq/tuxedo respond to incoming external pull requests in approximately 8.5 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 46.4 C-Rank™ score (B 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 46.4 places webstonehq/tuxedo in the B tier.

What is the external contributor pull request merge rate for webstonehq/tuxedo?

The external contributor pull request merge rate for webstonehq/tuxedo is 41.7%, based on public PR activity from non-core contributors.

Are there Good First Issues available in webstonehq/tuxedo?

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

webstonehq
webstonehq/tuxedoBSolid1.6k
GitHub
Back to Explorer
webstonehq

webstonehq/tuxedo

1,574
BSolid(46/100)Rust

A fast, keyboard-driven terminal UI for todo.txt.

Compare
Jump to:

AI Maintainer Review Guidelines

Review Persona

Welcoming Community Builder

Warmth Score
8.0/10
Patience Score
8.2/10
Nitpick Rate
45%

Collaborative maintainer environment in webstonehq/tuxedo. Reviews community pull requests with focus on project quality.

What Contributors Actually Say

Discussions in webstonehq/tuxedo focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.

Hidden Friction Signals

Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.

Unwritten Rules

  • 1) Keep PR scope strictly aligned with the linked issue.
  • 2) Ensure local linters pass before opening a review.
  • 3) Maintain full test coverage for modified logic.

Top PR Submission Do's

  • Link the issue and include reproduction context in the PR
  • Update docs or README when behavior changes
  • Add or update tests for changed behavior before requesting review

Top PR Friction Pitfalls (Don'ts)

  • Do not open context-free PRs
  • Do not ship user-facing changes without matching docs
  • Do not leave requested test coverage unresolved
Response Velocity
8 hours
Standard maintainer review cycle

Average Response Latency

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

Merge Efficiency
41.7%
Moderate PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
66.7%
Strong first-timer PR acceptance rate

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
9 core
Highly collaborative maintainer core
Diagnostic Health HUD
41.7%
Merge Gauge
66.7%
1st-Timer
Community Vibe60/100

Embed C-Rank Badge

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

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

Active Good First Issues (0)

View on GitHub

No cached good first issues currently tracked for webstonehq/tuxedo.

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 webstonehq/tuxedo

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

Frequently Asked Questions - Contributing to webstonehq/tuxedo

01

Is webstonehq/tuxedo welcoming to first-time open-source contributors?

webstonehq/tuxedo has a recorded first-timer success rate of 66.7%. Repositories ranked Solid 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 ~8 hours. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 46.4 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 46.4 places webstonehq/tuxedo in the Solid tier.

04

What is the external contributor pull request merge rate for webstonehq/tuxedo?

The external pull request merge rate is 41.7%. 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 webstonehq/tuxedo?

webstonehq/tuxedo 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 webstonehq/tuxedo 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.