Mod manager and Modding IDE for League of Legends.
C-Rank Grade: A (Welcoming) - 62/100
External PR Merge Rate: 24%
Response Time: -
First Timer Success: 100%
LeagueToolkit/ltk-manager has a recorded first-timer success rate of 100.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in LeagueToolkit/ltk-manager respond to incoming external pull requests in approximately 0.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 61.9 places LeagueToolkit/ltk-manager in the A tier.
The external contributor pull request merge rate for LeagueToolkit/ltk-manager is 24.2%, based on public PR activity from non-core contributors.
LeagueToolkit/ltk-manager does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
Mod manager and Modding IDE for League of Legends.
Rigorous architecture standards (100% critical review signals). Ensure PRs strictly follow guidelines before requesting review in LeagueToolkit/ltk-manager.
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/LeagueToolkit/ltk-manager?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 21:00 UTC (21:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 18:00 to 22:00 UTC (18:00 - 22:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (30% approval). Large PRs (>500 lines) take ~115 hours (15% approval). Keep your diff compact for rapid review.
Problem / Motivation Why doesn't this tool support the Asia server? We really need this feature. We used to use the LOL Mod Skin tool, but later it was detected by the official and got our accounts banned, making it unusable. Proposed Solution ... Alternatives Considered No response Additional Context No response
Description I had to repatch my whole LTK whenever i tried to test a new skin Steps to Reproduce Steps that i did : Downloaded LTK First time Imported from Cslol mods Patched the first time patch Tested one of the skins Has to repatch again after turning on and off Expected Behavior Have to repatch whole mod list Actual Behavior Have to repatch whole mod list App Version No response Operating System No response Additional Context No response
Description Using LTK Manager v0.5.0 with mods imported from CustomSkin for LoL prevents me from entering a League match after clicking Patch Starter. The client queues normally, but when the match should open, nothing happens. There is no error, warning, or crash. Playing without the patcher works normally. I also noticed a major slowdown in patching: the Building Overlay step takes around 12 minutes in the new manager, compared to about 3 minutes in the old mod manager. Steps to Reproduce Launch LTK Manager v0.5.0. Import existing mods from CustomSkin for LoL. Disable all chroma VFX mods as a test (issue still occurs). Click Patch Starter. Wait for patching to finish. Launch League of Legends, queue, and accept a match. Attempt to load into game. Expected Behavior The patcher should complete normally, the game should launch into the accepted match successfully with the imported mods enabled, and patching time should be roughly comparable to the old manager rather than taking signif
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 LeagueToolkit/ltk-manager, 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 LeagueToolkit/ltk-manager acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 24.2% were successfully merged into the primary branch.
LeagueToolkit/ltk-manager has a recorded first-timer success rate of 100.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~-. 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 61.9 places LeagueToolkit/ltk-manager in the Welcoming tier.
The external pull request merge rate is 24.2%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
LeagueToolkit/ltk-manager does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.
All metrics displayed for LeagueToolkit/ltk-manager 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.