.NET (WPF and Windows Forms) bindings for the Chromium Embedded Framework
C-Rank Grade: B (Solid) - 52/100
External PR Merge Rate: 56%
Response Time: 22h
First Timer Success: 75%
cefsharp/CefSharp has a recorded first-timer success rate of 75.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in cefsharp/CefSharp respond to incoming external pull requests in approximately 22.3 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 51.6 places cefsharp/CefSharp in the B tier.
The external contributor pull request merge rate for cefsharp/CefSharp is 56.3%, based on public PR activity from non-core contributors.
cefsharp/CefSharp currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Balanced & professional review environment in cefsharp/CefSharp. Maintains strict focus on technical quality and test standards.
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/cefsharp/CefSharp?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 02:00 UTC (02:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 00:00 to 04:00 UTC (00:00 - 04:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (70% approval). Large PRs (>500 lines) take ~115 hours (25% approval). Keep your diff compact for rapid review.
Describe the solution you'd like I moved from IContextMenuHandler to CefSharp.Wpf.Handler.ContextMenuHandler in order to avoid #1882. As a result, the context menu now has the default WPF styling, which doesn't really fit Chrome or modern Windows. I would like to be able to set the context menu's Style property; however, the context menu is instantiated ad-hoc, so this doesn't seem possible. I.e., I would like either a property ContextMenuStyle on CefSharp.Wpf.ChromiumWebBrowser to set the style beforehand, then if set, have CefSharp.Wpf.Handler.ContextMenuHandler apply it or an event ContextMenuCreated in CefSharp.Wpf.Handler.ContextMenuHandler which I can listen to Describe alternatives you've considered implementing IContextMenuHandler myself (or inheriting from CefSharp.Wpf.Handler.ContextMenuHandler. However, that seems like a lot of error-prone work. using CefSharp.Wpf.Handler.ContextMenuHandler but overriding RunContextMenu to grab the created ContextMenu. This doesn't (seem
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 cefsharp/CefSharp, 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 cefsharp/CefSharp acknowledge new external contributions in approximately 22 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 56.3% were successfully merged into the primary branch.
cefsharp/CefSharp has a recorded first-timer success rate of 75.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~22 hours. 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 51.6 places cefsharp/CefSharp in the Solid tier.
The external pull request merge rate is 56.3%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, cefsharp/CefSharp 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 cefsharp/CefSharp 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.