iOS Toolbox using the DarkSword kexploit. iOS 17.0 - iOS 18.7.1 & iOS 26.0.x, excluding M5 and A19.
C-Rank Grade: B (Solid) - 45/100
External PR Merge Rate: 67%
Response Time: 15d
First Timer Success: 67%
rooootdev/lara has a recorded first-timer success rate of 66.7%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in rooootdev/lara respond to incoming external pull requests in approximately 358.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 45.5 places rooootdev/lara in the B tier.
The external contributor pull request merge rate for rooootdev/lara is 67.0%, based on public PR activity from non-core contributors.
rooootdev/lara currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Balanced & professional review environment in rooootdev/lara. 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/rooootdev/lara?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 16:00 UTC (16:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 15:00 to 19:00 UTC (15:00 - 19:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~233 hours (84% approval). Large PRs (>500 lines) take ~1723 hours (30% approval). Keep your diff compact for rapid review.
Is your feature request related to a problem? It's frustrating when the system update notification appears in settings app. I want to disable it. Describe the solution you'd like: probably a button that reads "disable ota" and another "re-enable ota" Describe alternatives you've considered: tvOS mobileconfig, which expired recently a dns config that blocks the update server, but is said to be somewhat unstable another app called muteOTA, claimed to be based on lara, but failed to work on my device (probably because of the M series chip?) Scope: UI / UX change New exploit capability or device support Tweak / package management Persistence or boot behavior Logging, diagnostics, or error handling Build system / CI Documentation Other Additional context: as described in "alternatives", there's an app that might be useful. I didn't find any source of it but the download page is here:https://wwbsb.lanzouw.com/b00hrprgxc Are you willing to help implement this? Yes, I can submit a
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 rooootdev/lara, 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 rooootdev/lara acknowledge new external contributions in approximately 14 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 67.0% were successfully merged into the primary branch.
rooootdev/lara has a recorded first-timer success rate of 66.7%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~14 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 45.5 places rooootdev/lara in the Solid tier.
The external pull request merge rate is 67.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, rooootdev/lara currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for rooootdev/lara 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.