dividebysandwich/sdroxide - Open Source PR Review Scorecard

A native SDR client for many radios (CAT, TCI, HPSDR, RTLSDR, SoapySDR, SDRPlay and more), written in Rust, with native and web remote UI (WASM), integrated CW/RTTY/PSK Skimmer, many digi modes built in (FT8, RTTY, PSK, SSTV, FreeDV, etc), logbook, Winlink, 3D Space weather, propagation map, satellite mode, and much more!

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

External PR Merge Rate: 60%

Response Time: 6h

First Timer Success: -

Frequently Asked Questions

Is dividebysandwich/sdroxide welcoming to first-time open-source contributors?

dividebysandwich/sdroxide has a recorded first-timer success rate of 0.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 dividebysandwich/sdroxide respond to incoming external pull requests in approximately 6.4 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 52.7 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 52.7 places dividebysandwich/sdroxide in the B tier.

What is the external contributor pull request merge rate for dividebysandwich/sdroxide?

The external contributor pull request merge rate for dividebysandwich/sdroxide is 60.0%, based on public PR activity from non-core contributors.

Are there Good First Issues available in dividebysandwich/sdroxide?

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

dividebysandwich
dividebysandwich/sdroxideBSolid121
GitHub
Back to Explorer
dividebysandwich

dividebysandwich/sdroxide

121
BSolid(53/100)Rust

A native SDR client for many radios (CAT, TCI, HPSDR, RTLSDR, SoapySDR, SDRPlay and more), written in Rust, with native and web remote UI (WASM), integrated CW/RTTY/PSK Skimmer, many digi modes built in (FT8, RTTY, PSK, SSTV, FreeDV, etc), logbook, Winlink, 3D Space weather, propagation map, satellite mode, and much more!

Compare
Jump to:
Response Velocity
6 hours
Standard maintainer review cycle

Average Response Latency

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

Merge Efficiency
60.0%
Moderate PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
0.0%
No first-timer merges recorded in window

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
30 core
Highly collaborative maintainer core
Diagnostic Health HUD
60.0%
Merge Gauge
0.0%
1st-Timer
Community Vibe49/100

Embed C-Rank Badge

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

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

Active Good First Issues (2)

View on GitHub

This repository currently has 2 open good first issue tickets available for newcomers.

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 dividebysandwich/sdroxide

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

Frequently Asked Questions - Contributing to dividebysandwich/sdroxide

01

Is dividebysandwich/sdroxide welcoming to first-time open-source contributors?

dividebysandwich/sdroxide has a recorded first-timer success rate of 0.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 ~6 hours. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 52.7 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 52.7 places dividebysandwich/sdroxide in the Solid tier.

04

What is the external contributor pull request merge rate for dividebysandwich/sdroxide?

The external pull request merge rate is 60.0%. 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 dividebysandwich/sdroxide?

Yes, dividebysandwich/sdroxide currently has 2 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 dividebysandwich/sdroxide 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.