An almost stable Matrix client.
C-Rank Grade: S (Elite) - 76/100
External PR Merge Rate: 84%
Response Time: 13h
First Timer Success: 93%
SableClient/Sable has a recorded first-timer success rate of 93.3%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in SableClient/Sable respond to incoming external pull requests in approximately 13.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 75.8 places SableClient/Sable in the S tier.
The external contributor pull request merge rate for SableClient/Sable is 84.3%, based on public PR activity from non-core contributors.
SableClient/Sable currently has 13 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in SableClient/Sable. Reviews community pull requests with focus on project quality.
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/SableClient/Sable?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 15:00 UTC (15:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 13:00 to 17:00 UTC (13:00 - 17:00 UTC local).
Limited recent maintainer review activity recorded for this repository. Prediction based on heuristic baseline.
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~9 hours (96% approval). Large PRs (>500 lines) take ~64 hours (38% approval). Keep your diff compact for rapid review.
Enter your branch size and test coverage below to forecast review turnaround and get 1-click git splitting commands.
Alternative open-source projects with active maintainers in TypeScript.
Online problem-driven learning system
Real time communication for agents. Wake on message, channels, DMs and actions. Useful for orchestrating agents.
Harness brings Jest-style tests to real native environments so you can test TurboModules like you would test your React Native app: with JavaScript.
Describe the problem Emojis are available with different skin tones, e.g. These are not exposed in the emoji picker at all. Describe the solution you'd like I would like to see all the skin tones available in the picker and a setting for a default tone that is automatically applied to sending emojis without an explicit tone selected; e.g. with “dark” selected, :person_shrugging should send the appropriate version of that emoji for dark skin tone. Alternatives considered I suppose just 1., without also implementing 2? Additional context No response
Describe the problem When reacting to messages or sending emojis, any standard emoji used will appear in the recently used section on top of the emoji menu. However, custom emojis do not appear in the recently used section. Describe the solution you'd like It'd be great if custom emojis could be found in recently used. I have a server with 30+ custom emojis so sorting through them can be tedious at times. Alternatives considered No response Additional context No response
Describe the problem Description Currently, when Sable launches Element Call, it hardcodes call URL parameters in src/app/plugins/call/CallEmbed.ts. There is no mechanism to pass Element Call configuration options (like autoLeaveWhenOthersLeft) from the admin configuration. Reasoning I want to disable the automatic call termination when all other participants leave a call. This behavior is configured in Element Call via the autoLeave URL parameter, which defaults to true for DM-style calls. However, Sable never passes this parameter, so im guessing default is set to true for any calls. Technical Details Relevant Code: Sable: src/app/plugins/call/CallEmbed.ts (lines 78-93) constructs the widget URL SableCall: src/UrlParams.ts (line 504) reads the autoLeave parameter SableCall: src/state/CallViewModel/CallNotificationLifecycle.ts (lines 116-124) uses the autoLeaveWhenOthersLeft option What's Missing: Sable needs to: Read call configuration from config.json Pass these options as URL pa
Describe the problem My chat looks like this lol Literally washes away any actual messages in the chat. Describe the solution you'd like Simple toggle in either the client settings or server wide (preferred) that disables these messages. Alternatives considered No response Additional context Handled in src/app/hooks/timeline/useTimelineEventRenderer.tsx
Describe the problem Currently well fonts are for spaces or rooms Describe the solution you'd like I would like to be able to set font for my whole user account Alternatives considered No response Additional context Would be cool to have it in the profile settings
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 SableClient/Sable, 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 SableClient/Sable acknowledge new external contributions in approximately 13 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 84.3% were successfully merged into the primary branch.
SableClient/Sable has a recorded first-timer success rate of 93.3%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~13 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 75.8 places SableClient/Sable in the Elite tier.
The external pull request merge rate is 84.3%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, SableClient/Sable currently has 13 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for SableClient/Sable 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.