Trio - an automated insulin delivery system for iOS based on the OpenAPS algorithm with adaptations.
C-Rank Grade: A (Welcoming) - 60/100
External PR Merge Rate: 70%
Response Time: 1d
First Timer Success: 55%
nightscout/Trio has a recorded first-timer success rate of 55.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in nightscout/Trio respond to incoming external pull requests in approximately 25.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 60.4 places nightscout/Trio in the A tier.
The external contributor pull request merge rate for nightscout/Trio is 70.2%, based on public PR activity from non-core contributors.
nightscout/Trio does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
Balanced & professional review environment in nightscout/Trio. 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/nightscout/Trio?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 19:00 UTC (19:00 UTC in your timezone). Recommended submission window is Monday - Wednesday 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 (88% approval). Large PRs (>500 lines) take ~120 hours (32% approval). Keep your diff compact for rapid review.
Describe the bug The x-axis labels in statistics are not aligned properly. Attach a Log n/a To Reproduce Steps to reproduce the behavior: Open stats to a Glucose (by day) or insulin or meals chart Open your eyes Expected behavior x-axis labels should appear and be aligned as they used to Screenshots Setup Information (please complete the following information): Smartphone: Hardware: iPhone 17 Pro Max OS Version: iOS 27.0 (full release) Pump: Manufacturer: Tandem Model: Mobi CGM: Device: Dexcom G7 Manager app: DexKit Trio Version: Version Number: 0.8.4.109 Repo: mikeplante1/trio Git Reference: 93fe2e8 Technical Details Built with Xcode 27 (I presume it'd look fine building with Xcode 26, but have not tested)
Describe the bug On the Garmin Venu 2, the Alarm icon sits lower than the other icons in the same row on the Alpine Watchface (Connect IQ store). The other two icons in that row are correctly aligned with each other, which suggests this is not a Venu 2 hardware/display issue but rather an icon-level vertical offset problem at the Garmin compiler level. To Reproduce Install the Alpine Watchface from the Garmin Connect IQ store Open the watchface on a Garmin Venu 2 (should be the same on other Venu models) Observe the icon row containing the Alarm icon Note the Alarm icon sits visually lower than its neighbors Expected behavior The Alarm icon should be vertically aligned with the other icons in the same row, consistent with how all other icons render. Screenshots Setup Information Smartphone: Hardware: iPhone 11 Pro Max OS Version: 26.3 Pump: Manufacturer: Omnipod Model: Dash CGM: Device: Dexcom G7 Manager app: Dexcom App Trio Version: Version Number: v0.6.0.43 (1) feat/garmin 97c76f7 R
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 nightscout/Trio, 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 nightscout/Trio acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 70.2% were successfully merged into the primary branch.
nightscout/Trio has a recorded first-timer success rate of 55.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~1 days+. 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 60.4 places nightscout/Trio in the Welcoming tier.
The external pull request merge rate is 70.2%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
nightscout/Trio does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.
All metrics displayed for nightscout/Trio 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.