ingo-eichhorst/Irrlicht - Open Source PR Review Scorecard

Claude Code session lights in your macOS menu bar — 🟣 🟠 🟢 ✦

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

External PR Merge Rate: 94%

Response Time: 23h

First Timer Success: 33%

Frequently Asked Questions

Is ingo-eichhorst/Irrlicht welcoming to first-time open-source contributors?

ingo-eichhorst/Irrlicht has a recorded first-timer success rate of 33.3%. 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 ingo-eichhorst/Irrlicht respond to incoming external pull requests in approximately 22.6 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 73.2 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 73.2 places ingo-eichhorst/Irrlicht in the B tier.

What is the external contributor pull request merge rate for ingo-eichhorst/Irrlicht?

The external contributor pull request merge rate for ingo-eichhorst/Irrlicht is 94.3%, based on public PR activity from non-core contributors.

Are there Good First Issues available in ingo-eichhorst/Irrlicht?

ingo-eichhorst/Irrlicht currently has 6 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".

ingo-eichhorst
ingo-eichhorst/IrrlichtBSolid88
GitHub
Back to Explorer
ingo-eichhorst

ingo-eichhorst/Irrlicht

88
BSolid(73/100)Go

Claude Code session lights in your macOS menu bar — 🟣 🟠 🟢 ✦

Compare
Jump to:
Response Velocity
22 hours
Standard maintainer review cycle

Average Response Latency

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

Merge Efficiency
94.3%
High acceptance rate for external PRs

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
33.3%
Accepts new contributor PRs

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
1 core
Single maintainer review bottleneck
Diagnostic Health HUD
94.3%
Merge Gauge
33.3%
1st-Timer
Community Vibe61/100

Embed C-Rank Badge

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

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

Active Good First Issues (6)

View on GitHub

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

View all good first issues directly on GitHub

Looking for more Go beginner tasks?Explore Go 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 ingo-eichhorst/Irrlicht

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

Frequently Asked Questions - Contributing to ingo-eichhorst/Irrlicht

01

Is ingo-eichhorst/Irrlicht welcoming to first-time open-source contributors?

ingo-eichhorst/Irrlicht has a recorded first-timer success rate of 33.3%. 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 ~22 hours. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 73.2 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 73.2 places ingo-eichhorst/Irrlicht in the Solid tier.

04

What is the external contributor pull request merge rate for ingo-eichhorst/Irrlicht?

The external pull request merge rate is 94.3%. 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 ingo-eichhorst/Irrlicht?

Yes, ingo-eichhorst/Irrlicht currently has 6 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 ingo-eichhorst/Irrlicht 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.