moo-man/WFRP4e-FoundryVTT - Open Source PR Review Scorecard

The premiere system for running grim and perilous games of Warhammer Fantasy Role-play in the Foundry VTT environment.

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

External PR Merge Rate: 100%

Response Time: 1d

First Timer Success: 100%

Frequently Asked Questions

Is moo-man/WFRP4e-FoundryVTT welcoming to first-time open-source contributors?

moo-man/WFRP4e-FoundryVTT has a recorded first-timer success rate of 100.0%. 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 moo-man/WFRP4e-FoundryVTT respond to incoming external pull requests in approximately 24.0 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 64.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 64.4 places moo-man/WFRP4e-FoundryVTT in the B tier.

What is the external contributor pull request merge rate for moo-man/WFRP4e-FoundryVTT?

The external contributor pull request merge rate for moo-man/WFRP4e-FoundryVTT is 100.0%, based on public PR activity from non-core contributors.

Are there Good First Issues available in moo-man/WFRP4e-FoundryVTT?

moo-man/WFRP4e-FoundryVTT does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.

moo-man
moo-man/WFRP4e-FoundryVTTBSolid106
GitHub
Back to Explorer
moo-man

moo-man/WFRP4e-FoundryVTT

106
BSolid(64/100)JavaScript

The premiere system for running grim and perilous games of Warhammer Fantasy Role-play in the Foundry VTT environment.

Compare
Jump to:
Response Velocity
1 days+
Standard maintainer review cycle

Average Response Latency

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

Merge Efficiency
100.0%
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
1 core
Single maintainer review bottleneck
Diagnostic Health HUD
100.0%
Merge Gauge
100.0%
1st-Timer
Community Vibe82/100

Embed C-Rank Badge

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

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

Active Good First Issues (0)

View on GitHub

No cached good first issues currently tracked for moo-man/WFRP4e-FoundryVTT.

View all good first issues directly on GitHub

Looking for more JavaScript beginner tasks?Explore JavaScript 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 moo-man/WFRP4e-FoundryVTT

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

Frequently Asked Questions - Contributing to moo-man/WFRP4e-FoundryVTT

01

Is moo-man/WFRP4e-FoundryVTT welcoming to first-time open-source contributors?

moo-man/WFRP4e-FoundryVTT 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.

02

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

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

03

What does the 64.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 64.4 places moo-man/WFRP4e-FoundryVTT in the Solid tier.

04

What is the external contributor pull request merge rate for moo-man/WFRP4e-FoundryVTT?

The external pull request merge rate is 100.0%. 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 moo-man/WFRP4e-FoundryVTT?

moo-man/WFRP4e-FoundryVTT 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 moo-man/WFRP4e-FoundryVTT 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.