A mobile terminal workspace for Android and iOS with SSH, Mosh, SFTP, hardware-key auth, tmux helpers, and an optional local shell.
C-Rank Grade: S (Elite) - 73/100
External PR Merge Rate: 85%
Response Time: 1d
First Timer Success: 75%
gwitko/Conduit has a recorded first-timer success rate of 75.0%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in gwitko/Conduit respond to incoming external pull requests in approximately 27.5 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 73.3 places gwitko/Conduit in the S tier.
The external contributor pull request merge rate for gwitko/Conduit is 85.4%, based on public PR activity from non-core contributors.
gwitko/Conduit currently has 5 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in gwitko/Conduit. Prompt code reviews with positive guidance for new contributors.
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/gwitko/Conduit?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 00:00 UTC (00:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 00:00 to 04:00 UTC (00:00 - 04:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~18 hours (96% approval). Large PRs (>500 lines) take ~132 hours (38% approval). Keep your diff compact for rapid review.
On iPad, this renders as an iPhone app and doesn't scale up.
I have ‘set mouse=a’ in my .vimrc. When I connect with ssh in a standard session without tmux, I can easily and smoothly scroll the file while editing. When I use tmux with ssh, the scrolling in vim is difficult to get started. I can get it to work sometimes, but it's not consistent. When I use mosh, I haven't been able to scroll vim launched from either the shell or a tmux session. Can this be corrected at all?
I ain't no lawyer. If any issue is found please email me at [email protected]. (relevant since 1.4.0)
Add metadata to izzyondroid repo so users can get access to updates, new features and bug fixes faster
France seems to have some weird laws about encryption in apps. Apple wants me to provide some documenation. It would be nice if a french person could help me do that or actually anyone. I'm not a lawyer. I don't want to go to prison. I followed apples instruction to not release in France for now. Sacrebleu!!!!!!
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 gwitko/Conduit, 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 gwitko/Conduit acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 85.4% were successfully merged into the primary branch.
gwitko/Conduit has a recorded first-timer success rate of 75.0%. Repositories ranked Elite 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 73.3 places gwitko/Conduit in the Elite tier.
The external pull request merge rate is 85.4%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, gwitko/Conduit 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 gwitko/Conduit 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.