What does the 50.6 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 50.6 places id577/FS25_AdvancedDamageSystem in the B tier.

Back to Explorer

id577/FS25_AdvancedDamageSystem

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

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

Q: What is the external contributor pull request merge rate for id577/FS25_AdvancedDamageSystem?

The external contributor pull request merge rate for id577/FS25_AdvancedDamageSystem is 92.3%, based on public PR activity from non-core contributors.

264

B•Solid(51/100)Lua

Advanced Damage System mod for Farming Simulator 25

Compare•

Jump to:

AI Maintainer Review Guidelines

Review Persona

Constructive Code Reviewer

Warmth Score

7.4/10

Patience Score

7.8/10

Nitpick Rate

33%

Balanced & professional review environment in id577/FS25_AdvancedDamageSystem. Maintains strict focus on technical quality and test standards.

Top PR Submission Do's

•Add unit tests with >80% coverage for modified code paths
•Use conventional commit messages and clean branch names
•Link relevant GitHub issue ID in PR description pre-flight checklist

Top PR Friction Pitfalls (Don'ts)

•Do not submit unlinked PRs without referencing an existing issue
•Do not mix refactoring and feature logic into a single commit
•Do not ping maintainers repeatedly within 24 hours of opening

Response Velocity

6 days+

Standard maintainer review cycle

Average Response Latency

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

Merge Efficiency

92.3%

High acceptance rate for external PRs

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success

100.0%

Strong first-timer PR acceptance rate

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers

6 core

Highly collaborative maintainer core

Diagnostic Health HUD

92.3%

Merge Gauge

100.0%

1st-Timer

Community Vibe67/100

Embed C-Rank Badge

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

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

90-Day C-Rank Trajectory

11 snapshots

Historical health & responsiveness evolution

50.5/100B

Aug 21

+38.4

Aug 9Range: 12.1 – 56.6 ptsAug 21

PR Acceptance & Review Speed Forecast

Run Pre-flight PR CheckPrecomputed via Live PR Events

Overall Merge Odds

92.3%

External PR acceptance

First-Timer Rate

100.0%

First PR success rate

Median Response (p50)

146h

50% receive response in

Tail Latency (p90)

N/A

90% receive response in

Active Maintainers: 6

Optimal PR Submission Window

Maintainer review activity heatmap & prime window prediction

Tuesday - ThursdayConfidence: NaN%

Peak Review Hour

14:00 UTC

Calculating local time...

Primary Window

14:00 - 18:00 UTC

Calculating local time...

Active Maintainers

Heuristic Estimate

Detected: UTC

24-Hour Maintainer Activity Heatmap (UTC)

LowPeak

00:0006:0012:0018:0023:00

Maintainers are most responsive around 14:00 UTC (14:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 14:00 to 18:00 UTC (14:00 - 18:00 UTC local).

PR Size vs Review Speed

Best Pull Request Size for id577/FS25_AdvancedDamageSystem

Sweet Spot: < 150 lines

Small (<150 LOC)Recommended

4.0davg review

96% Merge Approval

Medium (150–500 LOC)Normal

9.1davg review

88% Merge Approval

Large (>500 LOC)Slow

29.3davg review

42% Merge Approval

Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~95 hours (96% approval). Large PRs (>500 lines) take ~702 hours (42% approval). Keep your diff compact for rapid review.

Interactive Test: Test your planned branch diff against id577/FS25_AdvancedDamageSystem's ~150 LOC sweet spot before opening a PR.

PR Merge Doctor · Pre-Submission Diff Check

Simulate Your PR Merge Speed

Enter your branch size and test coverage below to forecast review turnaround and get 1-click git splitting commands.

⚡ Sweet spot: ~150 LOC

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 Lua beginner tasks?Explore Lua 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 id577/FS25_AdvancedDamageSystem

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

Frequently Asked Questions - Contributing to id577/FS25_AdvancedDamageSystem

Is id577/FS25_AdvancedDamageSystem welcoming to first-time open-source contributors?

id577/FS25_AdvancedDamageSystem has a recorded first-timer success rate of 100.0%. Repositories ranked Solid 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?

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

What does the 50.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 50.6 places id577/FS25_AdvancedDamageSystem in the Solid tier.

What is the external contributor pull request merge rate for id577/FS25_AdvancedDamageSystem?

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

Are there beginner Good First Issues open in id577/FS25_AdvancedDamageSystem?

Yes, id577/FS25_AdvancedDamageSystem 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 id577/FS25_AdvancedDamageSystem 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.