Real-time two-way voice translator for VRChat — LLM-based, VR subtitle overlay & OSC
C-Rank Grade: A (Welcoming) - 56/100
External PR Merge Rate: 90%
Response Time: 5h
First Timer Success: -
kapitalismho/PuriPuly-heart has a recorded first-timer success rate of 0.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in kapitalismho/PuriPuly-heart respond to incoming external pull requests in approximately 5.5 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 56.5 places kapitalismho/PuriPuly-heart in the A tier.
The external contributor pull request merge rate for kapitalismho/PuriPuly-heart is 90.0%, based on public PR activity from non-core contributors.
kapitalismho/PuriPuly-heart currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Strict review standards in kapitalismho/PuriPuly-heart. Ensure PR scope matches issue requirements closely before requesting review.
Discussions in kapitalismho/PuriPuly-heart 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/kapitalismho/PuriPuly-heart?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 07:00 UTC (07:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 04:00 to 08:00 UTC (04:00 - 08:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (96% approval). Large PRs (>500 lines) take ~26 hours (40% approval). Keep your diff compact for rapid review.
Background The translation prompt references a short history of recent utterances to translate the current sentence. The prompt defines principles for when that context should be used and when it should be ignored. Currently only 7 language pairs have example files. Many language pairs are not yet covered, and your contribution would be greatly appreciated. Goal Create example files for language pairs. Please refer to prompts/prompt-examples/language-pair/ for the directory structure. The existing files in that directory are a useful reference. Guidelines Follow the style and format of the existing files. Each file should consist of one context-use example and one context-ignore example.
Background The translation prompt references per-language rule files for the target language — the language used when the other person's speech is translated for you to read. Currently only 4 languages are covered: english, japanese, korean, chinese We would like to support more languages and improve translation quality overall, and we would appreciate your help in creating rules for your native language. Revisions to the existing rule files are also welcome. Goal Turn the "this sounds a bit unnatural" moments you notice in machine translation into generalizable rules, and add them to the files. Please refer to prompts/prompt-rules/target-language/ for the directory structure. The existing files in that directory are a useful reference. Suggested Approach Use the existing files in the same directory as a reference. Keep each rule to a single concise line. Follow the style of the existing rules.
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 kapitalismho/PuriPuly-heart, 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 kapitalismho/PuriPuly-heart acknowledge new external contributions in approximately 5 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 90.0% were successfully merged into the primary branch.
kapitalismho/PuriPuly-heart has a recorded first-timer success rate of 0.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~5 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 56.5 places kapitalismho/PuriPuly-heart in the Welcoming tier.
The external pull request merge rate is 90.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, kapitalismho/PuriPuly-heart 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 kapitalismho/PuriPuly-heart 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.