A decentralized and private (end-to-end encrypted) financial safety net for you and your friends.
C-Rank Grade: B (Solid) - 59/100
External PR Merge Rate: 57%
Response Time: <1h
First Timer Success: 100%
okTurtles/group-income has a recorded first-timer success rate of 100.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in okTurtles/group-income respond to incoming external pull requests in approximately 0.2 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 58.6 places okTurtles/group-income in the B tier.
The external contributor pull request merge rate for okTurtles/group-income is 57.1%, based on public PR activity from non-core contributors.
okTurtles/group-income currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
A decentralized and private (end-to-end encrypted) financial safety net for you and your friends.
Active maintainer team in okTurtles/group-income 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/okTurtles/group-income?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 02:00 UTC (02:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 01:00 to 05:00 UTC (01:00 - 05:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (71% approval). Large PRs (>500 lines) take ~1 hours (26% approval). Keep your diff compact for rapid review.
Problem While testing 2.9.0 we noticed (and documented, AIs see comments in #3154) high memory usage in the app, going up to over 1GB+ when first logging into existing chatrooms from scratch in a fresh session (and then slowly going down, but remaining high). Attempts to fix this included optimizations to how the journal was being used: #3162 okTurtles/libcheloniajs#99 Then we later noticed that actually this high memory usage preceded 2.9.0 and existed in 2.8.0 in a fresh session as well. The good news is that while testing master with 2.9.0 (specifically in 6b7627c, a few commits after v2.9.0), the memory usage goes down significantly if you close the tab and re-open it. So the issue seems to happen primarily when loading the website on a new device and logging in to an existing account that has a large chatroom. Chrome seems to have trouble clearing the memory of all the message objects that are loaded in this situation. Solution It is unclear what the solution is, it might not be
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 okTurtles/group-income, 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 okTurtles/group-income acknowledge new external contributions in approximately <1 hour. Out of all submitted pull requests from non-core authors in the last 180-day window, 57.1% were successfully merged into the primary branch.
okTurtles/group-income has a recorded first-timer success rate of 100.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~<1 hour. 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 58.6 places okTurtles/group-income in the Solid tier.
The external pull request merge rate is 57.1%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, okTurtles/group-income 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 okTurtles/group-income 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.