A KernelSU based root solution for Android
C-Rank Grade: A (Welcoming) - 61/100
External PR Merge Rate: 60%
Response Time: 4h
First Timer Success: 42%
ReSukiSU/ReSukiSU has a recorded first-timer success rate of 41.7%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in ReSukiSU/ReSukiSU respond to incoming external pull requests in approximately 4.2 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 60.6 places ReSukiSU/ReSukiSU in the A tier.
The external contributor pull request merge rate for ReSukiSU/ReSukiSU is 60.2%, based on public PR activity from non-core contributors.
ReSukiSU/ReSukiSU does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
Collaborative maintainer environment in ReSukiSU/ReSukiSU. Reviews community pull requests with focus on project quality.
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/ReSukiSU/ReSukiSU?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 02:00 UTC (02:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 02:00 to 06:00 UTC (02:00 - 06:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (75% approval). Large PRs (>500 lines) take ~20 hours (27% approval). Keep your diff compact for rapid review.
Please check before submitting an issue / 提交 Issue 前请确认 I have read the documents, and haven't found anything relevant / 我已阅读文档，且未找到相关内容 I surely I'm using the latest CI manager which is from main branch / 我确定我使用的是来自 main 分支的最新 CI 管理器 I have searched the issues and haven't found anything relevant / 我已搜索过 Issue 且未找到相关内容 I will upload bugreport file in KernelSU Manager - Settings - Report log / 我将在 KernelSU 管理器 - 设置 - 报告日志 中上传 bugreport 文件 I know how to reproduce the issue which may not be specific to my device / 我知道如何复现该问题，且该问题可能不局限于我的设备 Kernel Version Category / 内核版本分类 5.10- Using LKM Mode? / 是否使用 LKM 模式？ No / 否 Hook Type / Hook 类型 manual Describe the bug / 描述 Bug No creation of .gitmodules when adding ReSukiSU to the kernel for the first time. Used curl -LSs
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 ReSukiSU/ReSukiSU, 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 ReSukiSU/ReSukiSU acknowledge new external contributions in approximately 4 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 60.2% were successfully merged into the primary branch.
ReSukiSU/ReSukiSU has a recorded first-timer success rate of 41.7%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~4 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 60.6 places ReSukiSU/ReSukiSU in the Welcoming tier.
The external pull request merge rate is 60.2%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
ReSukiSU/ReSukiSU 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 ReSukiSU/ReSukiSU 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.