Zero-Trust access management with true WireGuard® 2FA/MFA
C-Rank Grade: S (Elite) - 69/100
External PR Merge Rate: 86%
Response Time: -
First Timer Success: 88%
DefGuard/defguard has a recorded first-timer success rate of 87.5%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in DefGuard/defguard 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.
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 69.4 places DefGuard/defguard in the S tier.
The external contributor pull request merge rate for DefGuard/defguard is 86.5%, based on public PR activity from non-core contributors.
DefGuard/defguard currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in DefGuard/defguard. Prompt code reviews with positive guidance for new contributors.
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/DefGuard/defguard?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 12:00 UTC (12:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 07:00 to 11:00 UTC (07:00 - 11:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (96% approval). Large PRs (>500 lines) take ~115 hours (39% approval). Keep your diff compact for rapid review.
Problem description Provide UI visibility into the serial numbers of connected devices Solves: Identification of unauthorized device registrations Troubleshooting one device versus another Proposed solution User profile > User devices > Add "Serial number" below "Public IP" Alternatives considered No response Impact Nice to have
Problem description "Client Configuration Permissions" and "Client traffic policy" shouldn't be a product wide setting. We want to allow certain users to create manual WireGuard configurations or allow some users to allow all traffic. Proposed solution Make "Client Configuration Permissions" and "Client traffic policy" a user/group-based setting. Alternatives considered No response Impact Important
Description As and administrator I would like to have a dedicated screen in the location that will show all associated devices with this location. Best would be to see all the info about the device: what user is the owner of the device what is the IP(s) of the device when it was last connected (or if it's still connected) from where it was connected (IP) - and maybe flag (of the country and geolocation info, city?) Also would be good to have some filters like: only connected now, never connected, connected within DATE-TIME RANGE, search the name and IP address (may be in one field)
Problem description We have many IPs that we need to configure for split tunnel - this is quite cumbersome with the current text field in a Location's "Allowed ips" that's present in the 1.6.*. release. It's hard to see what is present (and whether it's valid) and edit what's already there. Proposed solution An improvement might be a managed table, with a single (validated) IP input box as the means to add new entries. The table itself could provide a way to remove entries, and if the IPs could be sorted that would be useful too. I'm thinking along the lines of how some networking apps manage the entry of MAC addresses for wifi endpoint allow lists, that kind of thing. Alternatives considered No response Impact Nice to have
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 DefGuard/defguard, 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 DefGuard/defguard acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 86.5% were successfully merged into the primary branch.
DefGuard/defguard has a recorded first-timer success rate of 87.5%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~-. 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 69.4 places DefGuard/defguard in the Elite tier.
The external pull request merge rate is 86.5%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, DefGuard/defguard currently has 3 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for DefGuard/defguard 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.