The official Foundry VTT implementation of the Daggerheart system
C-Rank Grade: S (Elite) - 72/100
External PR Merge Rate: 83%
Response Time: 16h
First Timer Success: 50%
Foundryborne/daggerheart has a recorded first-timer success rate of 50.0%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in Foundryborne/daggerheart respond to incoming external pull requests in approximately 16.0 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
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 72.3 places Foundryborne/daggerheart in the S tier.
The external contributor pull request merge rate for Foundryborne/daggerheart is 83.3%, based on public PR activity from non-core contributors.
Foundryborne/daggerheart currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
The official Foundry VTT implementation of the Daggerheart system
Highly welcoming maintainers in Foundryborne/daggerheart. Prompt code reviews with positive guidance for new contributors.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/Foundryborne/daggerheart?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 11:00 UTC (11:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 20:00 to 00:00 UTC (20:00 - 00:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (96% approval). Large PRs (>500 lines) take ~115 hours (37% approval). Keep your diff compact for rapid review.
Describe the bug When dragging items/features/domain cards, etc. the artwork is shown in full size on firefox in the drag preview. this looks really bad with high resolution artwork, and a maximum size should be set here. To Reproduce Steps to reproduce the behavior: 1.open a game in firefox 2. create a character 3. drag anything during character creation/when using 4. especially visible with high resolution artwork/domain cards
Subclass descriptions often don't match the actual book description or have a line break where there shouldn't be. For example. vs
The google font imports can run into issues of reliability, either with the developer's internet connection or with google's. We should replace them with font files in the project itself, and set up the font families,
Description I've seen in a game a scenario where people were trying to aid, and it got lost who was aiding. A suggestion was pitched to add some means in the sheet to spend hope to aid and post in the chat that the player is aiding a roll. There may or may not be automation for it beyond the hope cost, but the very act of signaling in the chat could be useful?
Description The basic domain cards are Spells, Abilities and Grimoires. I'd like to request the possibility to add a homebrew type, if that can be done.
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to Foundryborne/daggerheart, 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 Foundryborne/daggerheart acknowledge new external contributions in approximately 16 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 83.3% were successfully merged into the primary branch.
Foundryborne/daggerheart has a recorded first-timer success rate of 50.0%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~16 hours. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
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 72.3 places Foundryborne/daggerheart in the Elite tier.
The external pull request merge rate is 83.3%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, Foundryborne/daggerheart currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for Foundryborne/daggerheart 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.