MeshAddicts/meshinfo - Open Source PR Review Scorecard

Realtime web UI to run against a Meshtastic regional or private mesh network.

C-Rank Grade: A (Welcoming) - 57/100

External PR Merge Rate: 98%

Response Time: -

First Timer Success: 100%

Frequently Asked Questions

Is MeshAddicts/meshinfo welcoming to first-time open-source contributors?

MeshAddicts/meshinfo has a recorded first-timer success rate of 100.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.

How fast can I expect code review feedback on my pull request?

Maintainers in MeshAddicts/meshinfo 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.

What does the 57.3 C-Rank™ score (A Tier) represent?

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 57.3 places MeshAddicts/meshinfo in the A tier.

What is the external contributor pull request merge rate for MeshAddicts/meshinfo?

The external contributor pull request merge rate for MeshAddicts/meshinfo is 98.2%, based on public PR activity from non-core contributors.

Are there Good First Issues available in MeshAddicts/meshinfo?

MeshAddicts/meshinfo currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".

MeshAddicts
MeshAddicts/meshinfoA•Welcoming146
GitHub
Back to Explorer
MeshAddicts

MeshAddicts/meshinfo

146
InactiveA•Welcoming(57/100)TypeScript

Realtime web UI to run against a Meshtastic regional or private mesh network.

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Strict Architecture Gatekeeper

Warmth Score
7.3/10
Patience Score
8.0/10
Nitpick Rate
30%

Strict review standards in MeshAddicts/meshinfo. Ensure PR scope matches issue requirements closely before requesting review.

Top PR Submission Do's

  • •Ensure code complies with the project coding style
  • •Keep PRs scoped to a single concern
  • •Include context and link to the related issue

Top PR Friction Pitfalls (Don'ts)

  • •Do not submit PRs without linking an issue
  • •Do not break existing tests without fixing them
  • •Do not mix unrelated refactors in a single PR
Response Velocity
-
No reviewer activity recorded

Average Response Latency

Tracks hours until a maintainer leaves a review, comment, or PR response.

Merge Efficiency
98.2%
High acceptance rate for external PRs

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
100.0%
Strong first-timer PR acceptance rate

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
1 core
Single maintainer review bottleneck
Diagnostic Health HUD
98.2%
Merge Gauge
100.0%
1st-Timer
Community Vibe69/100

Embed C-Rank Badge

Show contributors that your repository actively reviews and merges external pull requests.

GetMerged C-Rank badge for MeshAddicts/meshinfo
[![GetMerged C-Rank](https://getmerged.abhishekco.de/api/badge/MeshAddicts/meshinfo)](https://getmerged.abhishekco.de/MeshAddicts/meshinfo?utm_source=github&utm_medium=badge)

Active Good First Issues (1)

View on GitHub

feat(map/rf): expand hardware & antenna catalogs and put the data to work across the RF tools Summary The RF tool suite (Coverage, Scan, LOS, presets) shares two hand-curated catalogs in frontend/src/pages/map/rf/coverageAnalysis.ts: COMMON_HARDWARE (~12 boards + Custom) and COMMON_ANTENNAS (7 omnis). Entries are thin — hardware is just label / txDbm / chipset, antennas just label / dbi — and several fields the tools already support are unpopulated or hardcoded. We should (1) enrich the schema, (2) add more boards/antennas, and (3) actually consume the richer data in the tools. Current state HardwareEntry.sensitivityOffsetDb exists and is plumbed through effectiveSensitivityDbm() into Coverage/Scan/LOS, but every entry leaves it at 0 ("until measured"). Cable loss is a hardcoded 0.5 dB in the link budget (coverageRaster.ts) and panel copy. Mesh-wide live coverage assumes every node is an SX1262 (liveCoverageParams.ts). Nodes report a Meshtastic HardwareModel (already shown as phot

📅 Opened Aug 2, 2026💬 0 comments
Quality: 80/100Contribute
Looking for more TypeScript beginner tasks?Explore TypeScript GFI

Contributor Community Vibe Feedback

Rate what actually matters after opening a pull request here.

Have you contributed to this repo?

Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.

3 ratings required
Maintainer helpfulness
Review speed
Beginner friendliness

Contributor Compatibility & Review Speed Analysis for MeshAddicts/meshinfo

When evaluating whether to contribute to MeshAddicts/meshinfo, 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 MeshAddicts/meshinfo acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 98.2% were successfully merged into the primary branch.

Frequently Asked Questions - Contributing to MeshAddicts/meshinfo

01

Is MeshAddicts/meshinfo welcoming to first-time open-source contributors?

MeshAddicts/meshinfo has a recorded first-timer success rate of 100.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.

02

How fast can I expect code review feedback on my pull request?

The initial maintainer response time averages ~-. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 57.3 C-Rank™ score represent?

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 57.3 places MeshAddicts/meshinfo in the Welcoming tier.

04

What is the external contributor pull request merge rate for MeshAddicts/meshinfo?

The external pull request merge rate is 98.2%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.

05

Are there beginner Good First Issues open in MeshAddicts/meshinfo?

Yes, MeshAddicts/meshinfo currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.

GetMerged C-Rank™ Indexing Standard

All metrics displayed for MeshAddicts/meshinfo 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.