はちみーをなめると〜 Game enhancement and translation mod for Honse Game. Cutting edge.
C-Rank Grade: S (Elite) - 76/100
External PR Merge Rate: 82%
Response Time: 7h
First Timer Success: 57%
kairusds/Hachimi-Edge has a recorded first-timer success rate of 57.1%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in kairusds/Hachimi-Edge respond to incoming external pull requests in approximately 7.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 75.7 places kairusds/Hachimi-Edge in the S tier.
The external contributor pull request merge rate for kairusds/Hachimi-Edge is 81.8%, based on public PR activity from non-core contributors.
kairusds/Hachimi-Edge currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Strict review standards in kairusds/Hachimi-Edge. Ensure PR scope matches issue requirements closely before requesting review.
Discussions in kairusds/Hachimi-Edge focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.
Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.
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/kairusds/Hachimi-Edge?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 01:00 UTC (01:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 00:00 to 04:00 UTC (00:00 - 04:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~5 hours (96% approval). Large PRs (>500 lines) take ~34 hours (37% approval). Keep your diff compact for rapid review.
Plugin version: 0.27.0 Game version (as shown in Komoe launcher): 1.0.1.0 OS: Windows 11 24H2 Issues: 1. Komoe or TW server is not listed under the installer's game version selection. Selecting DMM works (the game provides a UnityPlayer.dll under KOMOE Game\komoemumamusume\komoemumamusume Game) but the generated umamusume.exe.local folder must be manually renamed to komoeumamusume.exe.local 2. Logging into a new Komoe account fails with "incorrect username or password" if the plugin is loaded. The game can switch between previously logged-in accounts normally, however 3. "Open config editor" from the plugin menu crashes the game Others: If a config option is modified via the in-game menu and then "Reload config", changes to config.json (and the option) are reverted. This includes toggling vsync, rebinding "menu_open_key" in "Open first time setup", etc. Manually editing config.json works as usual The plugin's in-game browser does not work, even when "ingame_webview" is set to true. It
Like custom font using extra_asset_bundle in config to replace utx_obj_title_logo_umamusume or other texture2d in resource.asset
a request from Ame in the discord, that I thought might be useful for accessibility / other purposes currently the font face used in-game is tightly controlled by the translation repo (specifically its config.json file), which itself is tightly controlled by the update checker's blake3 hashing. If one edits their localized_data/config.json to point to a different font & font name, the update checker will detect changes & replace said file with the default, preventing users who need/want custom fonts from updating their TL repo without going back to manually re-apply their changes. this is problematic given the frequency of TL repo updates. a workaround exists by creating an excludes.txt file in Hachimi's main data directory, but this prevents localized data's config.json from being updated entirely, which still isn't perfect one possible solution would be to allow the TL repo to provide a "sane default" font & add a separate entry in the main config to override the font, if enabled (wi
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 kairusds/Hachimi-Edge, 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 kairusds/Hachimi-Edge acknowledge new external contributions in approximately 7 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 81.8% were successfully merged into the primary branch.
kairusds/Hachimi-Edge has a recorded first-timer success rate of 57.1%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~7 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 75.7 places kairusds/Hachimi-Edge in the Elite tier.
The external pull request merge rate is 81.8%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, kairusds/Hachimi-Edge 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 kairusds/Hachimi-Edge 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.