Cross-platform & feature rich iOS/iPadOS/tvOS sideloading application. Formerly known as PlumeImpactor.
C-Rank Grade: A (Welcoming) - 60/100
External PR Merge Rate: 36%
Response Time: 2d
First Timer Success: 100%
claration/Impactor has a recorded first-timer success rate of 100.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in claration/Impactor respond to incoming external pull requests in approximately 41.3 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 59.7 places claration/Impactor in the A tier.
The external contributor pull request merge rate for claration/Impactor is 36.4%, based on public PR activity from non-core contributors.
claration/Impactor currently has 5 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Strict review standards in claration/Impactor. Ensure PR scope matches issue requirements closely before requesting review.
Discussions in claration/Impactor 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/claration/Impactor?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 23:00 UTC (23:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 20:00 to 00:00 UTC (20:00 - 00:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~27 hours (45% approval). Large PRs (>500 lines) take ~198 hours (16% approval). Keep your diff compact for rapid review.
Content Environment iOS version: 26.4.2 Impactor version: 2.6.3 LiveContainer+SideStore Nightly: build from Sep 11 Description I installed LiveContainer+SideStore Nightly using Impactor.When trying to install LiveContainer2, I got an error: Failed to Install LiveContainer2 com.kdt.LiveContainer2 could not be found. Additional observation Installing the same build of LiveContainer+SideStore Nightly via iLoader works fine, and I don't encounter this error. Could anyone help me resolve this issue? Thanks a lot!
Content Found a crash in Impactor 2.6.1 (macOS 15.7.7, arm64) repro: click Add Tweak → while the file picker is open, drag a file onto it → abort it's the blocking rfd. package.rs calls rfd::FileDialog::new()...pick_files() straight inside Iced's update(), 4 spots: 156 AddTweak 171 AddBundle 198 SetCustomIcon 218 SetCustomEntitlements that blocks the event loop inside -[NSSavePanel runModal]. AppKit spins a nested runloop for the modal, a drag comes in via NSCoreDragTrackingProc and dispatches back into the app while update() is still on the stack → re-entry → panic → abort. crash log matches frame for frame: 39 -[NSSavePanel runModal] 21 NSCoreDragTrackingProc 19 -[NSRunLoop runMode:beforeDate:] 15 CFRUNLOOP_IS_CALLING_OUT_TO_A_BLOCK 2 abort fix is already in the repo — subscriptions.rs:461 uses rfd::AsyncFileDialog with .await. those 4 just need Task::perform instead of blocking + Task::none(). side note, probably same root cause: the Tweaks section has no drop target
Content This error occurs during the installation of an IPA file when signing it with an Apple ID. How can I fix it?
Content I tried to sideload an .ipa but it showed this error. I've signed in with Apple ID and have tried adhoc but to no avail. The link to the .ipa should be attached below. https://www.mediafire.com/file/0pojuqvsti50k6z/TheSpikeCross-TNK-7.0.107%25282%2529.ipa/file?dkey=v1nzhvdvrnm&r=1971 Thanks a lot.
Content
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 claration/Impactor, 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 claration/Impactor acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 36.4% were successfully merged into the primary branch.
claration/Impactor has a recorded first-timer success rate of 100.0%. Repositories ranked Welcoming 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 59.7 places claration/Impactor in the Welcoming tier.
The external pull request merge rate is 36.4%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, claration/Impactor currently has 5 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for claration/Impactor 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.