💊 Application to use ReVanced on Android
C-Rank Grade: B (Solid) - 51/100
External PR Merge Rate: 31%
Response Time: 1d
First Timer Success: 38%
ReVanced/revanced-manager has a recorded first-timer success rate of 37.5%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in ReVanced/revanced-manager respond to incoming external pull requests in approximately 24.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 50.6 places ReVanced/revanced-manager in the B tier.
The external contributor pull request merge rate for ReVanced/revanced-manager is 31.0%, based on public PR activity from non-core contributors.
ReVanced/revanced-manager currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Balanced & professional review environment in ReVanced/revanced-manager. Maintains strict focus on technical quality and test standards.
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/ReVanced/revanced-manager?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 20:00 UTC (20:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 18:00 to 22:00 UTC (18:00 - 22:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (39% approval). Large PRs (>500 lines) take ~116 hours (15% approval). Keep your diff compact for rapid review.
Bug description The scroll indicator on the patch selection page does not work and jumps to an arbitrary position when hitting the end of the list. Record_2026-03-18-17-34-09_a85b47aaa863e3bc831e16d29c27a79c.mp4 Patch logs Debug logs revanced-manager_logcat_2026-03-18T17_32_49.332124.txt Acknowledgements I have checked all open and closed bug reports and this is not a duplicate. I have chosen an appropriate title. All requested information has been provided properly. The bug is only related to ReVanced Manager.
Feature description I was initially thinking off removing the select patches button, but then users wouldnt see the list of patches. So when the safeguard is enabled Instead of "Select patches" it could say "View patches". The view would show checked and unchecked patches but on selection, it would show the usual safeguard dialog. Motivation Select patches implies they can select patches, while view patches communicates that they cant change the selection. In the list they can see the checkmarks though, which invites them to test checking prompting them the safeguard which finally clarifies that it is technically possible to change the selection but its recommended to use the default. A seamless introduction through the features. Acknowledgements I have checked all open and closed feature requests and this is not a duplicate. I have chosen an appropriate title. The feature request is only related to ReVanced Manager.
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 ReVanced/revanced-manager, 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 ReVanced/revanced-manager acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 31.0% were successfully merged into the primary branch.
ReVanced/revanced-manager has a recorded first-timer success rate of 37.5%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~1 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 50.6 places ReVanced/revanced-manager in the Solid tier.
The external pull request merge rate is 31.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, ReVanced/revanced-manager 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 ReVanced/revanced-manager 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.