Modern networking and security platform providing secure access and connectivity to apps, infrastructure, and AI workloads. Connect and protect your users.
C-Rank Grade: A (Welcoming) - 67/100
External PR Merge Rate: 67%
Response Time: 2d
First Timer Success: 69%
fosrl/pangolin has a recorded first-timer success rate of 68.8%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in fosrl/pangolin respond to incoming external pull requests in approximately 54.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 66.8 places fosrl/pangolin in the A tier.
The external contributor pull request merge rate for fosrl/pangolin is 67.2%, based on public PR activity from non-core contributors.
fosrl/pangolin currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Modern networking and security platform providing secure access and connectivity to apps, infrastructure, and AI workloads. Connect and protect your users.
Highly encouraging & supportive maintainers (75% positive review sentiment). Active code reviews with constructive guidance for new contributors in fosrl/pangolin.
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/fosrl/pangolin?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 21:00 UTC (21:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 18:00 to 22:00 UTC (18:00 - 22:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~35 hours (84% approval). Large PRs (>500 lines) take ~259 hours (30% approval). Keep your diff compact for rapid review.
Describe the Bug Pangolin's browser-based RDP feature (built on IronRDP, since v1.19) authenticates via CredSSP, which negotiates down to NTLM for the Windows logon. NTLM cannot resolve Azure AD-only joined identities (no on-prem AD, no hybrid join), so RDP into any cloud-only Azure AD joined Windows device fails outright, regardless of correct credentials. This is a protocol-level failure, not a configuration or credentials issue. The target machine's Event Viewer shows every attempt failing locally in the NTLM stack: Failure Reason: Unknown user name or bad password Status: 0xC000006D Sub Status: 0xC0000064 (account does not exist) Authentication Package: NTLM The failure is identical across every username format (AzureAD\user, [email protected], DOMAIN\user). Entra ID sign-in logs show no sign-in attempt at all for these connections, confirming Azure AD is never reached, the connection dies in Windows' local NTLM stack before any cloud validation occurs. This also rules out Conditio
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 fosrl/pangolin, 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 fosrl/pangolin acknowledge new external contributions in approximately 2 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 67.2% were successfully merged into the primary branch.
fosrl/pangolin has a recorded first-timer success rate of 68.8%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~2 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 66.8 places fosrl/pangolin in the Welcoming tier.
The external pull request merge rate is 67.2%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, fosrl/pangolin currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for fosrl/pangolin 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.