marcoroth/herb - Open Source PR Review Scorecard

🌿 Powerful and seamless HTML-aware ERB toolchain.

C-Rank Grade: S (Elite) - 71/100

External PR Merge Rate: 88%

Response Time: 9h

First Timer Success: 67%

Frequently Asked Questions

Is marcoroth/herb welcoming to first-time open-source contributors?

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

What does the 71.5 C-Rankâ„¢ score (S 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 71.5 places marcoroth/herb in the S tier.

What is the external contributor pull request merge rate for marcoroth/herb?

The external contributor pull request merge rate for marcoroth/herb is 88.1%, based on public PR activity from non-core contributors.

Are there Good First Issues available in marcoroth/herb?

marcoroth/herb currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".

marcoroth
marcoroth/herbS•Elite1.3k
GitHub
Back to Explorer
marcoroth

marcoroth/herb

1,287
S•Elite(71/100)TypeScript

🌿 Powerful and seamless HTML-aware ERB toolchain.

Compare•
Jump to:
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
88.1%
High acceptance rate for external PRs

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
26 core
Highly collaborative maintainer core
Diagnostic Health HUD
88.1%
Merge Gauge
66.7%
1st-Timer
Community Vibe79/100

Embed C-Rank Badge

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

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

Active Good First Issues (1)

View on GitHub

This repository currently has 1 open good first issue tickets available for newcomers.

View all good first issues directly on GitHub

Looking for more TypeScript beginner tasks?Explore TypeScript 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 marcoroth/herb

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

Frequently Asked Questions - Contributing to marcoroth/herb

01

Is marcoroth/herb welcoming to first-time open-source contributors?

marcoroth/herb has a recorded first-timer success rate of 66.7%. Repositories ranked Elite 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 71.5 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 71.5 places marcoroth/herb in the Elite tier.

04

What is the external contributor pull request merge rate for marcoroth/herb?

The external pull request merge rate is 88.1%. 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 marcoroth/herb?

Yes, marcoroth/herb currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.

GetMerged C-Rankâ„¢ Indexing Standard

All metrics displayed for marcoroth/herb 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.

marcoroth/herb • 71.5/100 C-Rank (S-Tier) | GetMerged