Real-time osu!mania overlay for tosu that estimates difficulty, analyzes Pattern/MSD, and visualizes graph + pause data for 4K, 6K, and 7K maps.
C-Rank Grade: A (Welcoming) - 62/100
External PR Merge Rate: 61%
Response Time: -
First Timer Success: 50%
LeoBlackMT/osumania_map_analyser has a recorded first-timer success rate of 50.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in LeoBlackMT/osumania_map_analyser 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 62.4 places LeoBlackMT/osumania_map_analyser in the A tier.
The external contributor pull request merge rate for LeoBlackMT/osumania_map_analyser is 60.9%, based on public PR activity from non-core contributors.
LeoBlackMT/osumania_map_analyser currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Growing JavaScript project in LeoBlackMT/osumania_map_analyser welcoming community pull requests and bug fixes.
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/LeoBlackMT/osumania_map_analyser?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 09:00 UTC (09:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 11:00 to 15:00 UTC (11:00 - 15:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (76% approval). Large PRs (>500 lines) take ~115 hours (27% approval). Keep your diff compact for rapid review.
下面转至我在mania tracker上的bug report。 Follow up on my last bug report, after I had some plays with Inverse + OD6 in the ranked section, I found out that the Sunny Angorithm seems to really bloat the SR / Dan estimate of songs with low bpm, particularly ones below 120 BPM. Some examples include: glow [7k Normal] [6th mid/low] (https://osu.ppy.sh/beatmapsets/117757#mania/303259) Destr0yer [Beginner] [6th low] (https://osu.ppy.sh/beatmapsets/875074#mania/1829711) Himeboshi [EZ] [5th mid/high] (https://osu.ppy.sh/beatmapsets/135412#mania/339287) In these songs, putting DT on lowers the star and dan rating, suprisingly. I assume this has to do with the release of the LN being further apart from the head, counting as different objects and bloating the SR. I think a simple solution to this would be to just excluse these plays on low BPM inverse songs altogether. I checked and only 0th to 2nd contains inverse maps near that BPM / density range (90, 105, 138), which are the da
RT 因为自己才刚3（4 low左右？），有点想贡献一点低星的难度分级，同时也在做自己的低星rf alt，所以提这个issue。 低星对于速技还是相对比较明确的，比如说160 MJS或者85-90的单乱大乱大概是3 mid，180 MJS是4 high/5 low这样。 中等程度的叠，像是90中叠大叠是4 mid，120的中叠大概是6 mid之类（？） 但小叠这种到底该算多难自己一直没数。 举几个例子： gulyayu(sped up ver.) 3.47 109 minijack poster boy 3.18 111 minijack cross over 3.10 132 minijack alice in mystic garden 3.59 134 Low CJ rabbit in the black room 3.39 135 minijack dragon lady 3.06 150 minijack/vibro（开DT会发现这首曲子被判到VIBRO） made of fire 3.29 162 jacky JS 在当前的Roxy Rework算法下，它们的难度依次是：2.52、3.24、3.28、4.03、3.02、3.28、2.82 作为参照，一些常见的小叠曲及其在Roxy Rework下得到的星数： reg3v3 jack 3.54，144 jacky JS，3.88 rf4v2 jack 3.8
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 LeoBlackMT/osumania_map_analyser, 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 LeoBlackMT/osumania_map_analyser acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 60.9% were successfully merged into the primary branch.
LeoBlackMT/osumania_map_analyser has a recorded first-timer success rate of 50.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 62.4 places LeoBlackMT/osumania_map_analyser in the Welcoming tier.
The external pull request merge rate is 60.9%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, LeoBlackMT/osumania_map_analyser 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 LeoBlackMT/osumania_map_analyser 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.