MTProxy for Telegram on Rust + Tokio
C-Rank Grade: A (Welcoming) - 59/100
External PR Merge Rate: 90%
Response Time: -
First Timer Success: 100%
telemt/telemt 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 telemt/telemt respond to incoming external pull requests in approximately 0.0 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.2 places telemt/telemt in the A tier.
The external contributor pull request merge rate for telemt/telemt is 90.0%, based on public PR activity from non-core contributors.
telemt/telemt currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Active maintainer team in telemt/telemt welcoming community pull requests and bug fixes.
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/telemt/telemt?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 18:00 UTC (18:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday 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 (96% approval). Large PRs (>500 lines) take ~115 hours (40% approval). Keep your diff compact for rapid review.
On 1 april 2026 I have faced issue with unable to connect from any kind of mobile platforms. Steps to reproduce try to connect from mobile device Log Apr 01 10:37:05 **** telemt[93734]: 2026-04-01T10:37:05.273362Z WARN telemt::maestro::listeners: Connection closed with error peer=AA.AA.AA.AA:56758 error=Telegram handshake timeout Apr 01 10:39:11 **** telemt[93734]: 2026-04-01T10:39:11.279624Z WARN telemt::maestro::listeners: Connection closed with error peer=BB.BB.BB.BB:37232 error=Telegram handshake timeout Apr 01 10:41:17 **** telemt[93734]: 2026-04-01T10:17:05.284846Z WARN telemt::maestro::listeners: Connection closed with error peer=CC.CC.CC.CC:35100 error=Telegram handshake timeout Additional info Lan connection (home wifi): issue occured mobile operators: issue occured OSs: Android/iOS telemt version: -- 3.3.16 -- 3.3.35 host location: Netherlands for non mobile clients everything looks perfect so far -- Linux clinet works well -- MacOs client works well Config # ==
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 telemt/telemt, 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 telemt/telemt acknowledge new external contributions in approximately -. 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.
telemt/telemt 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 ~-. 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.2 places telemt/telemt in the Welcoming 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, telemt/telemt 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 telemt/telemt 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.