Because no one should manage diabetes alone 💙
C-Rank Grade: A (Welcoming) - 68/100
External PR Merge Rate: 81%
Response Time: 3h
First Timer Success: 50%
lumose-health/GlycemicGPT 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 lumose-health/GlycemicGPT respond to incoming external pull requests in approximately 2.7 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 68.3 places lumose-health/GlycemicGPT in the A tier.
The external contributor pull request merge rate for lumose-health/GlycemicGPT is 81.4%, based on public PR activity from non-core contributors.
lumose-health/GlycemicGPT currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Active maintainer team in lumose-health/GlycemicGPT 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/lumose-health/GlycemicGPT?utm_source=github&utm_medium=badge)
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 - Thursday from 17:00 to 21:00 UTC (17:00 - 21: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 ~4 hours (96% approval). Large PRs (>500 lines) take ~13 hours (37% 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 Python.
A fork of FreeCAD that has a clanker brain.
Practical productivity tools for Claude Code, Codex-CLI, and similar CLI coding agents.
Knowhere extracts, parses, and outputs structured chunks ready for AI Agents and RAG.
Summary The one-time CareLink Connect pairing helper (tools/connect-helper) drives a Chromium-family browser over the DevTools protocol to capture the login. The UI and docs say it works with "Chrome, Edge, Brave, or Chromium", but in practice it only auto-detects Chrome and Chromium, not Brave and not Edge, and there is no way to point it at an installed browser. Reported in #708: a Mac user with Brave/Safari/Firefox could not pair and had to use Chrome on a separate Windows machine; same on Linux with Brave, where it "kept asking for Chrome." Why it happens The helper uses chromedp.DefaultExecAllocatorOptions (tools/connect-helper/main.go) with no chromedp.ExecPath override and no --browser flag. chromedp v0.15.1's findExecPath searches only Chrome and Chromium binaries/standard paths on every OS (macOS: Google Chrome.app / Chromium.app; Linux: google-chrome* / chromium*; Windows: Chrome/Chromium paths). It never looks for Brave or Edge. A Brave-only user hits the "is Chrome/Edge in
Summary The one-time CareLink historical import appears to fail for EU / non-US accounts. Reported in #708 (MiniMed 780G, European CareLink): the user connects fine and reaches the date-range picker, but the import itself errors out. Diagnosis so far Reaching the date picker means CareLink auth, the region host (carelink.minimed.eu), and the availability lookup all succeeded, so the failure is isolated to the report-export step (generate report -> poll status -> download CSV). That step was only ever validated against a US account; the EU host was built from the same pattern but never verified end-to-end against a real EU account. Likely divergence points, all of which currently collapse into one generic error: the reportStatus response body not matching our readiness check (the poll times out or fetches the CSV too early), the downloaded CSV not matching the expected header / delimiter (EU locale uses semicolons and decimal commas), response field names in generateReport / /patient/u
We've shipped two independent ways to get Medtronic data into GlycemicGPT, and we'd love feedback from people actually using them. If you have a Medtronic pump, trying either path and telling us how it went — whether it worked as expected, or you hit any issues — is the single most useful thing you can do to help these improve. Both are read-only — GlycemicGPT only reads your data; it never sends anything to your pump or changes any setting. The two paths 1. Bluetooth pairing (on-device, mobile app) — pair a MiniMed 680G / 770G / 780G directly to your phone over Bluetooth, no Medtronic account needed. Docs: Pairing your Medtronic pump over Bluetooth 2. CareLink cloud sync (web) — pull pump + CGM data from Medtronic CareLink, with continuous sync and one-time historical import. Docs: Connecting your Medtronic pump (CareLink) They're unrelated; you can use either or both. What we'd most like you to check Please sanity-check the values GlycemicGPT shows against your pump (or Car
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 lumose-health/GlycemicGPT, 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 lumose-health/GlycemicGPT acknowledge new external contributions in approximately 2 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 81.4% were successfully merged into the primary branch.
lumose-health/GlycemicGPT 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 ~2 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 68.3 places lumose-health/GlycemicGPT in the Welcoming tier.
The external pull request merge rate is 81.4%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, lumose-health/GlycemicGPT currently has 3 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for lumose-health/GlycemicGPT 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.