基于自定义规则的番剧采集APP，支持流媒体在线观看，支持弹幕，支持实时超分辨率。
C-Rank Grade: A (Welcoming) - 58/100
External PR Merge Rate: 54%
Response Time: 4d
First Timer Success: 55%
Predidit/Kazumi has a recorded first-timer success rate of 55.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in Predidit/Kazumi respond to incoming external pull requests in approximately 91.9 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 58.1 places Predidit/Kazumi in the A tier.
The external contributor pull request merge rate for Predidit/Kazumi is 53.6%, based on public PR activity from non-core contributors.
Predidit/Kazumi currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Responsive & active maintainer team in Predidit/Kazumi. Reviews pull requests with focus on project architectural goals.
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/Predidit/Kazumi?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 03:00 UTC (03:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 03:00 to 07:00 UTC (03:00 - 07:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~60 hours (67% approval). Large PRs (>500 lines) take ~441 hours (24% approval). Keep your diff compact for rapid review.
issue 内容 希望iOS版本播放界面能够侧滑返回，目前该界面侧滑返回没反应 提交前确认 issue 列表中，没有我的新功能需求 / 问题
issue 内容 流量播放时，会在刚进入播放时自动缓存整集，有时只是因为更换源而需要观看其中一小部分确定是否正确，但这样对流量需求较大，建议增加使用流量观看时只缓存所选位置之后30s左右即可 提交前确认 issue 列表中，没有我的新功能需求 / 问题
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 Predidit/Kazumi, 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 Predidit/Kazumi acknowledge new external contributions in approximately 3 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 53.6% were successfully merged into the primary branch.
Predidit/Kazumi has a recorded first-timer success rate of 55.0%. Repositories ranked Welcoming 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 58.1 places Predidit/Kazumi in the Welcoming tier.
The external pull request merge rate is 53.6%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, Predidit/Kazumi 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 Predidit/Kazumi 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.