A Rust library for managing NetworkManager connections over D-Bus.
C-Rank Grade: B (Solid) - 48/100
External PR Merge Rate: 50%
Response Time: 1d
First Timer Success: -
freedesktop-rs/nmrs 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.
Maintainers in freedesktop-rs/nmrs respond to incoming external pull requests in approximately 27.5 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 48.3 places freedesktop-rs/nmrs in the B tier.
The external contributor pull request merge rate for freedesktop-rs/nmrs is 50.0%, based on public PR activity from non-core contributors.
freedesktop-rs/nmrs currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in freedesktop-rs/nmrs. Reviews community pull requests with focus on project quality.
Discussions in freedesktop-rs/nmrs focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.
Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.
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/freedesktop-rs/nmrs?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 00:00 UTC (00:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 21:00 to 01:00 UTC (21:00 - 01:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~18 hours (62% approval). Large PRs (>500 lines) take ~132 hours (22% approval). Keep your diff compact for rapid review.
pop-os/cosmic-applets#1224 the D-Bus device proxy already has set_autoconnect and Managed properties wired up in dbus/device.rs, but these are not surfaced in the public NetworkManager API. set_wireless_enabled exists as a global radio toggle for wifi. there is no equivalent for ethernet — consumers cannot implement an "ethernet on/off" toggle without reaching through to nm.dbus_connection() and building their own proxy. exposing set_device_autoconnect(iface, bool) and/or set_device_managed(iface, bool) on NetworkManager would cover this.
pop-os/cosmic-settings#2087 NetworkManager exposes a writable GlobalDnsConfiguration property on /org/freedesktop/NetworkManager. nmrs has no support for reading or writing it. this blocks COSMIC settings from offering a "change DNS servers globally" option — currently users can only set DNS per-connection.
core/custom_connection.rs builds bluetooth specific_object with bluez_device_path(bdaddr, None), so multi-adapter hosts always get hci0. read the adapter from bluetooth settings if present, related to #210.
NetworkManager::set_wireless_enabled rustdoc says it replaces the deprecated set_wifi_enabled, but set_wifi_enabled is still public and not deprecated. fix the wording in nmrs/src/api/network_manager.rs.
Describe the issue The wifi.rs module has no unit tests, we should add some similar to bluetooth.rs.
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 freedesktop-rs/nmrs, 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 freedesktop-rs/nmrs acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 50.0% were successfully merged into the primary branch.
freedesktop-rs/nmrs 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.
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 48.3 places freedesktop-rs/nmrs in the Solid tier.
The external pull request merge rate is 50.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, freedesktop-rs/nmrs 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 freedesktop-rs/nmrs 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.