Mod Manager for Paradox Games. Official Discord: https://discord.gg/t9JmY8KFrV
C-Rank Grade: B (Solid) - 49/100
External PR Merge Rate: 100%
Response Time: 16h
First Timer Success: -
bcssov/IronyModManager has a recorded first-timer success rate of 0.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in bcssov/IronyModManager respond to incoming external pull requests in approximately 16.4 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 49.3 places bcssov/IronyModManager in the B tier.
The external contributor pull request merge rate for bcssov/IronyModManager is 100.0%, based on public PR activity from non-core contributors.
bcssov/IronyModManager currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Rigorous architecture standards (66% critical review signals). Ensure PRs strictly follow guidelines before requesting review in bcssov/IronyModManager.
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/bcssov/IronyModManager?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 15:00 UTC (15:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 12:00 to 16:00 UTC (12:00 - 16:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~11 hours (96% approval). Large PRs (>500 lines) take ~79 hours (45% approval). Keep your diff compact for rapid review.
I apologize in advance for the tone. I have debated for some time if I should open a feature suggestion or not, given it as been refused a number of times. But I always come back to it because of frustration. The text below has been written in multiple waves of frustrations and is a bit of a mix between a feature suggestion and a "frustration rant". I've tried to edit it to be less of a rant without removing necessary details. My use case I sometimes forget to properly sort my mods, or verify load order on the mod page and I accidentally mess up my load order way too often : sort load order by mod name, accidental drag and drop, click on wrong arrow, and other user caused issues. Dyspraxia and trying to "make precise movements in reasonable timeframe" don't mix well in any context (and the frustration of messing up the load order while trying to fix the previous mess up doesn't help with that problem either). I'm eternally thankful for the undo/redo and import/export features, but auto
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 bcssov/IronyModManager, 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 bcssov/IronyModManager acknowledge new external contributions in approximately 16 hours. 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.
bcssov/IronyModManager has a recorded first-timer success rate of 0.0%. Repositories ranked Solid 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 49.3 places bcssov/IronyModManager in the Solid tier.
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.
Yes, bcssov/IronyModManager currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for bcssov/IronyModManager 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.