Status App client made in Nim & QML
C-Rank Grade: A (Welcoming) - 68/100
External PR Merge Rate: 70%
Response Time: 15h
First Timer Success: 54%
status-im/status-app has a recorded first-timer success rate of 53.8%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in status-im/status-app respond to incoming external pull requests in approximately 15.4 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 67.5 places status-im/status-app in the A tier.
The external contributor pull request merge rate for status-im/status-app is 70.5%, based on public PR activity from non-core contributors.
status-im/status-app currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Active maintainer team in status-im/status-app 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/status-im/status-app?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 13:00 UTC (13:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 13:00 to 17:00 UTC (13:00 - 17:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~10 hours (88% approval). Large PRs (>500 lines) take ~74 hours (32% approval). Keep your diff compact for rapid review.
Bug Report Description When clearing group chat history, the messages are deleted but not chat information such as: created the group change group's name left the group has added This information also is sent to new group chat members. When I added chair to my group chat he did not get the messages but got the chat info. Screenshot from his device: This behaviour happens for members who were already in the chat and just cleared their history. Steps to reproduce Make a Group Chat Add / Remove members and rename group chat Clear Chat history / Add new member Expected behaviour Empty chat Actual behaviour Additional Information Operating System and version: Windows 10 - 2.38.0 MacBook Pro 16-inch Nov 2024; Sequoia 15.6 - 2.38.1
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 status-im/status-app, 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 status-im/status-app acknowledge new external contributions in approximately 15 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 70.5% were successfully merged into the primary branch.
status-im/status-app has a recorded first-timer success rate of 53.8%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~15 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 67.5 places status-im/status-app in the Welcoming tier.
The external pull request merge rate is 70.5%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, status-im/status-app 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 status-im/status-app 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.