ML-powered manga translator, written in Rust.
C-Rank Grade: B (Solid) - 55/100
External PR Merge Rate: 45%
Response Time: 3d
First Timer Success: 40%
mayocream/koharu has a recorded first-timer success rate of 40.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in mayocream/koharu respond to incoming external pull requests in approximately 78.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 54.8 places mayocream/koharu in the B tier.
The external contributor pull request merge rate for mayocream/koharu is 45.1%, based on public PR activity from non-core contributors.
mayocream/koharu does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
Rigorous architecture standards (80% critical review signals). Ensure PRs strictly follow guidelines before requesting review in mayocream/koharu.
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/mayocream/koharu?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 05:00 UTC (05:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 02:00 to 06:00 UTC (02:00 - 06:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~52 hours (61% approval). Large PRs (>500 lines) take ~387 hours (22% approval). Keep your diff compact for rapid review.
I'd like to hear your opinion on how to improve the automatic layout. For example: Should the font size follow the original font size? Should it allow the text to overflow the bubble? In which cases? If the text is free text, what are the bounds (text bbox) of the text? ...etc It would be helpful if you could provide an example image for each use case.
does koharu can't utilize shared gpu memory? because im using sugoi 14b ultra models and sometimes it just stop translating after dedicated memory is full my system is using rtx 3060 12Gb vram intel core i5 10400f and 64Gb ram. so i have about 32gb shared memory sugoi 14b ultra model is really nice at translating, thats why i like it even it is slower than vntl-llama3-8b-v2.
Japanese name can translate to different name if it's represented in kana. Use NER models to extract those name/place entity and allow user to configure a map for static translation results
Last used LLM should be remembered. User should not need to read documents to find out which model to use for perferred language to translate to. Model list should indicate which models are already downloaded. [Optional] Downloaded model can be deleted
It should not be too large as it may translate to shorter words in other language; or should be too small to make it not readable at all.
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 mayocream/koharu, 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 mayocream/koharu acknowledge new external contributions in approximately 3 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 45.1% were successfully merged into the primary branch.
mayocream/koharu has a recorded first-timer success rate of 40.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~3 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 54.8 places mayocream/koharu in the Solid tier.
The external pull request merge rate is 45.1%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
mayocream/koharu 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 mayocream/koharu 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.