Open-source Flutter client for MeshCore LoRa mesh networking devices
C-Rank Grade: A (Welcoming) - 65/100
External PR Merge Rate: 68%
Response Time: 1d
First Timer Success: 57%
zjs81/meshcore-open has a recorded first-timer success rate of 57.1%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in zjs81/meshcore-open respond to incoming external pull requests in approximately 32.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 64.8 places zjs81/meshcore-open in the A tier.
The external contributor pull request merge rate for zjs81/meshcore-open is 67.6%, based on public PR activity from non-core contributors.
zjs81/meshcore-open currently has 4 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Balanced & professional review environment in zjs81/meshcore-open. 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/zjs81/meshcore-open?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 ~21 hours (85% approval). Large PRs (>500 lines) take ~154 hours (30% approval). Keep your diff compact for rapid review.
Summary Expose advanced repeater controls in the repeater settings screen and wire refresh actions for those settings. Context Current repeater settings UI does not expose all advanced controls that are available/expected for power users. Proposed Scope Add an "Advanced settings" section/card in repeater settings UI Include controls for: interference threshold AGC reset interval flood max hops multi-ACKs Add refresh actions for advanced fields Add l10n keys for new labels/actions Acceptance Criteria Advanced controls are visible and editable in repeater settings UI Refresh actions are available for each advanced setting App compiles cleanly and localized string keys exist for supported locales No unrelated behavior changes are included
As a user, I would like to have Public and hash channels clearly marked on the chat view as not being private as these keys are well-known. This can be accomplished by use of icons, colors, and labels. Additionally, as a user I would like to be able to mark private channels with the same "not private" status as keys can be published for anyone to see.
I had tried that but got the edit / delete menu so I didnt know you could move them. Maybe if they were highlighted in a different color or something like an outline around them on long press it might visually make the point better that they can be moved? I also thought the touch target may be a bit small. Perhaps: Highlight the card on long press/move select increase size of target
Is it possible to create a ‘Favourite GIFs’ block where you can add your favourite GIF files?
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 zjs81/meshcore-open, 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 zjs81/meshcore-open acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 67.6% were successfully merged into the primary branch.
zjs81/meshcore-open has a recorded first-timer success rate of 57.1%. 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 64.8 places zjs81/meshcore-open in the Welcoming tier.
The external pull request merge rate is 67.6%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, zjs81/meshcore-open currently has 4 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for zjs81/meshcore-open 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.