Open-source LoRa base station for Meshtastic/MeshCore. Raspberry Pi + SX1302/SX1303 concentrator: passive multi-channel capture, local dashboard, native TX
C-Rank Grade: D (Risky) - 8/100
External PR Merge Rate: -
Response Time: -
First Timer Success: -
KMX415/meshpoint has a recorded first-timer success rate of 0.0%. Repositories ranked D typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in KMX415/meshpoint 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 7.5 places KMX415/meshpoint in the D tier.
The external contributor pull request merge rate for KMX415/meshpoint is 0.0%, based on public PR activity from non-core contributors.
KMX415/meshpoint currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Active maintainer team in KMX415/meshpoint 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/KMX415/meshpoint?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 15:00 UTC (15:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 15:00 to 19:00 UTC (15:00 - 19:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (81% approval). Large PRs (>500 lines) take ~115 hours (29% approval). Keep your diff compact for rapid review.
What do you want to add? A Sort: Packets option on the local Meshpoint node grid, next to the existing Last heard / Signal / Hops / Name dropdown. Highest packet_count first. Same favorites pin and All / Direct / Relayed filters as the other sorts. Why is this useful? Node cards already store packet_count, and the node drawer already shows a Packets line. There is no way to rank the grid by who you hear most. Operators keep asking which node they get the most packets from. Today the answer is click nodes one by one, or a SQLite query on the Pi. Does this affect: Parsing Relay Radio Dashboard Installer Region support Extra notes Sort itself already shipped. frontend/js/node_cards.js SORT_KEYS is last_heard, signal, hops, name. frontend/js/node_cards_sort.js has no packets comparator. packet_count is on the node model and in to_dict(), so this should be frontend-only: one <option> in frontend/index.html and one case in _comparator. Null / zero packet counts at the end, same patte
Discussed in #33 Originally posted by Cryptocurrency4Sale April 27, 2026 Would it be possible to create a notification sound for incoming messages while browser tab or window is not in focus?
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 KMX415/meshpoint, 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 KMX415/meshpoint acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 0.0% were successfully merged into the primary branch.
KMX415/meshpoint has a recorded first-timer success rate of 0.0%. Repositories ranked Risky 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 7.5 places KMX415/meshpoint in the Risky tier.
The external pull request merge rate is 0.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, KMX415/meshpoint currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for KMX415/meshpoint 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.