🦴 2dog is Godot in .NET
C-Rank Grade: B (Solid) - 70/100
External PR Merge Rate: 94%
Response Time: 2d
First Timer Success: 100%
outfox/2dog 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.
Maintainers in outfox/2dog respond to incoming external pull requests in approximately 36.3 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 69.6 places outfox/2dog in the B tier.
The external contributor pull request merge rate for outfox/2dog is 94.1%, based on public PR activity from non-core contributors.
outfox/2dog currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in outfox/2dog. 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/outfox/2dog?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 14:00 UTC (14:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 12:00 to 16:00 UTC (12:00 - 16:00 UTC local).
Limited recent maintainer review activity recorded for this repository. Prediction based on heuristic baseline.
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~24 hours (96% approval). Large PRs (>500 lines) take ~174 hours (42% approval). Keep your diff compact for rapid review.
Enter your branch size and test coverage below to forecast review turnaround and get 1-click git splitting commands.
Alternative open-source projects with active maintainers in C#.
StackExchange.Redis.Extensions is a library that extends StackExchange.Redis, making it easier to work with Redis in .NET applications
.NET Reader for the MaxMind DB Database Format
Client-side changes to make multiplayer work
All of the showcase demos need to show 2 way interactions with mouse and key inputs working dnx 2dog new winforms -n MyGame showcase.winforms dnx 2dog new winformslib dnx 2dog new blazorwasm
My project uses a double precision build of Godot, which causes issues with 2dog's single precision build in nuget. Is building 2dog locally in double mode supported? If so, what's the process? Thanks!
godotengine/godot#70796 (comment) @zorbathut For what it's worth, I gave a shot turning LibGodot into a .NET web export, but I only had time to put a day or two into it. I got it to the point of loading Godot and trying to load the project at which point it died due to some weird conflict with the virtual filesystem, at which point I realized I needed to get back to my main project and scrapped it. I think it's a viable solution, and arguably better than the Mono solution, it's just not a priority for me right now. I've got some notes at the bottom of this page and my half-baked-at-best sourcecode here; I am happy to talk to people about this but I don't really have time to devote to coding it. @thygrrr thank you for active participation, create a issue here so we have a chance to follow your challenges, feedback etc. Hopefully we can attract others who could figure out how to make LibGodot works in e.g. winform, etc. as user control. A big unmet need in .NET ecosystem considering
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 outfox/2dog, 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 outfox/2dog acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 94.1% were successfully merged into the primary branch.
outfox/2dog 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.
The initial maintainer response time averages ~1 days+. 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 69.6 places outfox/2dog in the Solid tier.
The external pull request merge rate is 94.1%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, outfox/2dog currently has 3 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for outfox/2dog 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.