🔓 ipadecrypt is an open-source tool for downloading, patching and decrypting .ipa's with minimal user intervention on palera1n and dopamine jailbreaks
C-Rank Grade: B (Solid) - 53/100
External PR Merge Rate: 90%
Response Time: 2h
First Timer Success: 100%
londek/ipadecrypt has a recorded first-timer success rate of 100.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in londek/ipadecrypt respond to incoming external pull requests in approximately 1.6 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 53.0 places londek/ipadecrypt in the B tier.
The external contributor pull request merge rate for londek/ipadecrypt is 90.0%, based on public PR activity from non-core contributors.
londek/ipadecrypt currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in londek/ipadecrypt. Reviews community pull requests with focus on project quality.
Discussions in londek/ipadecrypt 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/londek/ipadecrypt?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 14:00 UTC (14:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 11:00 to 15:00 UTC (11:00 - 15:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (96% approval). Large PRs (>500 lines) take ~8 hours (40% approval). Keep your diff compact for rapid review.
With my current iDevice running with Taurine jailbreak, trying to decrypt Cult of the Lamb (https://apps.apple.com/us/app/cult-of-the-lamb/id1639580858) crashes the helper with exit code 132. C:\Users\User>ipadecrypt --redact decrypt https://apps.apple.com/us/app/cult-of-the-lamb/id1639580858 ✓ ipadecrypt v0.7.2 · [email protected] iOS 14.7.1 arm64 iPhone10,4 (unknown) ✓ signed in as ###### (###### storefront) ✓ found com.devolverdigital.cultofthelamb on App Store ✓ cached com.devolverdigital.cultofthelamb_1.4.13.ipa ✓ patched Info.plist ✓ MinimumOSVersion 16.0 → 14.7.1 ✓ installed → /var/containers/Bundle/Application/CA9C0F69-5C1B-4C07-A1D1-88CDDC955883/CultOfTheLamb.app · spawned com.devolverdigital.cultofthelamb via SBS (pid=1871) · decrypted main CultOfTheLamb (16.0 KB) · symtab patches: 2 (Diagnostics::error ret) ✗ assemble: helper exit 132 ✓ uninstalled com.devolverdigital.cultofthelamb I am currently confused why this sp
The README states ipadecrypt decrypts iOS 26 apps. Based on my file-format research on the FairPlay SC_Info key files (https://github.com/vnc0/fairplay-scinfo), there is a class of binaries where this cannot work on a pre-26 device. While the issue is currently only noticeable in a handful of apps, I expect it to affect a wider range of apps in the near future. Background iOS 26 introduced new SC_Info key-file variants — .v4.supp (version byte 0x04) and .v5.supf (0x05) — alongside the legacy .supp (0x01) / .supf (0x03). For most apps both generations ship side by side, so a pre-26 kernel can still use the legacy pair. For binaries that are iOS-26-only, Apple stops shipping the legacy pair: the .supp is absent and the .supf is truncated to 0 bytes, leaving only the new .v4.supp / .v5.supf. Examples in the wild: com.microsoft.rdc.ios 11.3.2 — main binary com.gopro.GoPro 13.34.1 — ReelSteady.framework Impact The v4/v5 key formats are only understood by the FairPlay subsystem on
Describe the bug ipadecrypt bootstrap fails on step 4. ▎ Step 4/4 · Install the decrypt helper A small embedded C binary that reads FairPlay-decrypted pages from a suspended task. Uploaded once to /var/mobile/Media/ipadecrypt/helpers/ and cached by SHA thereafter. ✗ verify failed: helper didn't respond with usage (got "") the device's code-signing layer rejected the helper's entitlements To Reproduce Steps to reproduce the behavior: Run ipadecrypt bootstrap while having a device with nathanlr connected Expected behavior No errors occur Environment nathanlr 2.1.1 iOS 17.0 iPad Air M1 Additional context Built from source, ran on macOS 26.4.
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 londek/ipadecrypt, 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 londek/ipadecrypt acknowledge new external contributions in approximately 1 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.
londek/ipadecrypt has a recorded first-timer success rate of 100.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~1 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 53.0 places londek/ipadecrypt in the Solid 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, londek/ipadecrypt currently has 3 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for londek/ipadecrypt 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.