koharu-rs/koharu - Open Source PR Review Scorecard

ML-powered manga translator, written in Rust.

C-Rank Grade: A (Welcoming) - 62/100

External PR Merge Rate: 35%

Response Time: -

First Timer Success: 40%

Frequently Asked Questions

Is koharu-rs/koharu welcoming to first-time open-source contributors?

koharu-rs/koharu has a recorded first-timer success rate of 40.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.

How fast can I expect code review feedback on my pull request?

Maintainers in koharu-rs/koharu 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.

What does the 62.1 C-Rank™ score (A Tier) represent?

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.1 places koharu-rs/koharu in the A tier.

What is the external contributor pull request merge rate for koharu-rs/koharu?

The external contributor pull request merge rate for koharu-rs/koharu is 34.6%, based on public PR activity from non-core contributors.

Are there Good First Issues available in koharu-rs/koharu?

koharu-rs/koharu currently has 46 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".

koharu-rs
koharu-rs/koharuA•Welcoming6.1k
GitHub
Back to Explorer
koharu-rs

koharu-rs/koharu

6,094
InactiveA•Welcoming(62/100)Rust

ML-powered manga translator, written in Rust.

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Empathetic Technical Mentor

Warmth Score
7.5/10
Patience Score
8.2/10
Nitpick Rate
20%

Collaborative maintainer environment in koharu-rs/koharu. Reviews community pull requests with focus on project quality.

What Contributors Actually Say

Discussions in koharu-rs/koharu focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.

Hidden Friction Signals

Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.

Unwritten Rules

  • •1) Keep PR scope strictly aligned with the linked issue.
  • •2) Ensure local linters pass before opening a review.
  • •3) Maintain full test coverage for modified logic.

Top PR Submission Do's

  • •Ensure code complies with the project coding style
  • •Keep PRs scoped to a single concern
  • •Include context and link to the related issue

Top PR Friction Pitfalls (Don'ts)

  • •Do not submit PRs without linking an issue
  • •Do not break existing tests without fixing them
  • •Do not mix unrelated refactors in a single PR
Response Velocity
-
No reviewer activity recorded

Average Response Latency

Tracks hours until a maintainer leaves a review, comment, or PR response.

Merge Efficiency
34.6%
Moderate PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
40.0%
Accepts new contributor PRs

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
12 core
Highly collaborative maintainer core
Diagnostic Health HUD
34.6%
Merge Gauge
40.0%
1st-Timer
Community Vibe26/100

Embed C-Rank Badge

Show contributors that your repository actively reviews and merges external pull requests.

GetMerged C-Rank badge for koharu-rs/koharu
[![GetMerged C-Rank](https://getmerged.abhishekco.de/api/badge/koharu-rs/koharu)](https://getmerged.abhishekco.de/koharu-rs/koharu?utm_source=github&utm_medium=badge)

Active Good First Issues (5)

View on GitHub

Description On Linux the WebGPU canvas is unavailable or falls back to software rendering on machines where the GPU stack is fine. crates/koharu-app/src/app.rs sets the WebGPU switches through Cef::command_line_args: .enable_features(["Vulkan", "VulkanFromANGLE"]) .command_line_args([ ("--enable-unsafe-webgpu", None), ("use-angle", Some("vulkan")), ("--ozone-platform", Some("x11")), ]) but in tauri-runtime-cef those switches are applied to the browser process only. Chromium builds each child process's command line from a fixed allowlist (ChromeContentBrowserClientCef::AppendExtraCommandLineSwitches) and drops everything else, so the GPU process never sees use-angle=vulkan or the Vulkan/VulkanFromANGLE feature names. The GPU process then initializes ANGLE on its default backend instead of Vulkan, and navigator.gpu reports no usable adapter ("webgpu found no adapters") — the canvas shows as unavailable or runs on SwiftShader. --ozone-platform=x11 (#1110) reached the GPU pro

📅 Opened Oct 4, 2026💬 3 comments
Quality: 90/100Contribute

Description Would be great to have selected text box to move by 1 pixel with directional key input. Thank you. Additional context No response

📅 Opened Sep 27, 2026💬 0 comments
Quality: 35/100Contribute

Description Suggestions for the local model catalog and defaults, from about a week of measuring models for manga translation into Spanish on a 16 GB VRAM GPU (RX 9060 XT) with 16 GB of system RAM. The numbers are small benchmarks graded against human translations, not a formal evaluation, but the gaps are large enough to be useful. Translation: Gemma 4 12B it QAT (already in the catalog as unsloth/gemma-4-12B-it-qat-GGUF; I run the lmstudio-community Q4_0 through LM Studio). It is the best local translator I found for this hardware. On 74 ambiguous lines that only their scene resolves, with a work note (see #339 and #1013): Source Gemma 4 12B DeepL English 7/8 3/8 Japanese 4/5 2/5 Chinese 4.7/5 3/5 Korean 88% 47% Qwen3 8B scored 71% on Korean, and EXAONE 3.5 7.8B (abliterated) 47%. On a real 23-page Japanese chapter (231 balloons), the full pipeline reached about 94% of balloons without a serious error. Two settings mattered a lot for Gemma: Thinking off. With reasoni

📅 Opened Sep 26, 2026💬 2 comments
Quality: 90/100Contribute

Description When you launch the application, nothing can be typed anywhere, including for the name of a new project. In the settings menus, nothing can be typed there either. Essentially, the application is completely unusable. Reverting back to version 0.83.0 fixes the problem. I would suspect that this issue is caused by the upgrade to Tauri v3 alpha (4a3c7b0), since it seems to be the only plausible culprit between 0.83.0 and 0.83.1. Steps to reproduce Open the application Click in the textbox for a new project name Attempt to type anything Your environment Koharu: 0.83.1 and later are affected OS: Fedora 44 KDE GPU: GeForce RTX 2060 Mobile Additional context No response

📅 Opened Sep 24, 2026💬 4 comments
Quality: 50/100Contribute

Issue Translation model pickers are empty with no error despite local hardcoded models being there. get_translation_models never resolves, so the list never updates. Cause openai-compatible and lm-studio ship default base URLs (http://localhost:11434/v1, http://localhost:1234), so they are probed even when unconfigured. The HTTP client has no read timeout and the providers are awaited together, so a probed localhost endpoint that never responds hangs the whole listing, local models are withheld too. Proposed Fixes Opt-in enabled switch (off by default) for openai-compatible and lm-studio. Make the base URLs blank by default so no provider is ever probed unless a URL is explicitly configured. Add a per-provider timeout (30s deadline) so one stalled endpoint no longer hangs the whole listing. Steps to reproduce Open the translation model dropdown. Your environment OS: Windows 11 Koharu: 0.82.1 Additional context No response

📅 Opened Sep 13, 2026💬 0 comments
Quality: 75/100Contribute
Looking for more Rust beginner tasks?Explore Rust GFI

Contributor Community Vibe Feedback

Rate what actually matters after opening a pull request here.

Have you contributed to this repo?

Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.

3 ratings required
Maintainer helpfulness
Review speed
Beginner friendliness

Contributor Compatibility & Review Speed Analysis for koharu-rs/koharu

When evaluating whether to contribute to koharu-rs/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 koharu-rs/koharu acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 34.6% were successfully merged into the primary branch.

Frequently Asked Questions - Contributing to koharu-rs/koharu

01

Is koharu-rs/koharu welcoming to first-time open-source contributors?

koharu-rs/koharu has a recorded first-timer success rate of 40.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.

02

How fast can I expect code review feedback on my pull request?

The initial maintainer response time averages ~-. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 62.1 C-Rank™ score represent?

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.1 places koharu-rs/koharu in the Welcoming tier.

04

What is the external contributor pull request merge rate for koharu-rs/koharu?

The external pull request merge rate is 34.6%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.

05

Are there beginner Good First Issues open in koharu-rs/koharu?

Yes, koharu-rs/koharu currently has 46 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.

GetMerged C-Rank™ Indexing Standard

All metrics displayed for koharu-rs/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.