hrzlgnm/mdns-browser - Open Source PR Review Scorecard

A cross platform mDNS-Browser app written in Rust using tauri and leptos

C-Rank Grade: B (Solid) - 70/100

External PR Merge Rate: 93%

Response Time: 1d

First Timer Success: 100%

Frequently Asked Questions

Is hrzlgnm/mdns-browser welcoming to first-time open-source contributors?

hrzlgnm/mdns-browser has a recorded first-timer success rate of 100.0%. Repositories ranked B 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 hrzlgnm/mdns-browser respond to incoming external pull requests in approximately 24.8 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 70.3 C-Rank™ score (B 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 70.3 places hrzlgnm/mdns-browser in the B tier.

What is the external contributor pull request merge rate for hrzlgnm/mdns-browser?

The external contributor pull request merge rate for hrzlgnm/mdns-browser is 92.8%, based on public PR activity from non-core contributors.

Are there Good First Issues available in hrzlgnm/mdns-browser?

hrzlgnm/mdns-browser does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.

hrzlgnm
hrzlgnm/mdns-browserBSolid177
GitHub
Back to Explorer
hrzlgnm

hrzlgnm/mdns-browser

177
BSolid(70/100)Rust

A cross platform mDNS-Browser app written in Rust using tauri and leptos

Compare
Jump to:
Response Velocity
1 days+
Standard maintainer review cycle

Average Response Latency

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

Merge Efficiency
92.8%
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
CRITICAL BUS FACTOR
Single maintainer
No active GitHub maintainers found (may review internally on Gerrit or internal tools)
Diagnostic Health HUD
92.8%
Merge Gauge
100.0%
1st-Timer
Community Vibe79/100

Embed C-Rank Badge

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

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

Active Good First Issues (0)

View on GitHub

No cached good first issues currently tracked for hrzlgnm/mdns-browser.

View all good first issues directly on GitHub

Looking for more Rust beginner tasks?Explore Rust 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 hrzlgnm/mdns-browser

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

Frequently Asked Questions - Contributing to hrzlgnm/mdns-browser

01

Is hrzlgnm/mdns-browser welcoming to first-time open-source contributors?

hrzlgnm/mdns-browser has a recorded first-timer success rate of 100.0%. Repositories ranked Solid 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 ~1 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 70.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 70.3 places hrzlgnm/mdns-browser in the Solid tier.

04

What is the external contributor pull request merge rate for hrzlgnm/mdns-browser?

The external pull request merge rate is 92.8%. 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 hrzlgnm/mdns-browser?

hrzlgnm/mdns-browser does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.

GetMerged C-Rank™ Indexing Standard

All metrics displayed for hrzlgnm/mdns-browser 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.