Robrix: a powerful multi-platform Matrix chat client written in Rust, using the Makepad UI toolkit and Robius platform abstractions
C-Rank Grade: A (Welcoming) - 59/100
External PR Merge Rate: 81%
Response Time: -
First Timer Success: 50%
project-robius/robrix has a recorded first-timer success rate of 50.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in project-robius/robrix 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.3 places project-robius/robrix in the A tier.
The external contributor pull request merge rate for project-robius/robrix is 81.1%, based on public PR activity from non-core contributors.
project-robius/robrix currently has 5 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Balanced & professional review environment in project-robius/robrix. Maintains strict focus on technical quality and test standards.
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/project-robius/robrix?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 22:00 UTC (22:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 21:00 to 01:00 UTC (21:00 - 01: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 (36% approval). Keep your diff compact for rapid review.
@matrix.org offers 2 different plans If you are on the premium plan the upload limit for an attachment is 100MB. Currently Robrix always display a warning when uploading files larger than 10MB. For a user on the @matrix.org on a premium plan that warning message is not correct. Not sure if there is a way to query which tier/plan of a home server a user has. If that feature exist it would be great if that could be shown under Account Settings in Robrix and popup messages adjusted accordingly.
When you get an invite from a another Matrix user for a chat e.g. join their room it is not well described. I believe Element is doing a better job here by adding the text: Do you want to chat with xxx?" I suggest Robrix is doing something similar.
If the current logged-in user can edit a space, then we also need to allow them to: Add rooms or subspaces to the space. Remove rooms or subspaces from the space. Mark rooms or subspaces as "suggested" (or not). Here are some screenshots from Element showing how they display it.
When trying via AppImageUpdate This is a common standard for updating AppImages. AppImage having update information would also recognized by other software e.g. AppImageLauncher info: https://github.com/AppImageCommunity/AppImageUpdate#update-information-overview https://github.com/AppImage/AppImageSpec/blob/master/draft.md#update-information
If the current user is removed (kicked or banned) from a joined room while that room is currently open in Robrix, then the RoomScreen should be updated to reflect that they are no longer a part of that room. Currently, the room is properly removed from the RoomsList, but the RoomScreen itself does not change, which is likely confusing to the user as it looks like they are still a joined member of the room and able to interact within it. There are two possible designs we could adopt here: Show a footer, similar to the TombstoneFooter in the RoomInputBar, that displays the status of their membership in that room (whether they were joined or banned) and a button to re-join or knock on that room (if permitted). This allows the user to still see the content of the room they were removed from, but not to send any messages. Hide the entire RoomScreen, and show only the content of the footer, but in a full view similar to the InviteScreen. This prevents the user from seeing the room at al
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 project-robius/robrix, 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 project-robius/robrix acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 81.1% were successfully merged into the primary branch.
project-robius/robrix has a recorded first-timer success rate of 50.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.3 places project-robius/robrix in the Welcoming tier.
The external pull request merge rate is 81.1%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, project-robius/robrix 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 project-robius/robrix 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.