Sentry SDK for .NET
C-Rank Grade: A (Welcoming) - 60/100
External PR Merge Rate: 70%
Response Time: 3d
First Timer Success: 71%
getsentry/sentry-dotnet has a recorded first-timer success rate of 71.4%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in getsentry/sentry-dotnet respond to incoming external pull requests in approximately 61.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 60.1 places getsentry/sentry-dotnet in the A tier.
The external contributor pull request merge rate for getsentry/sentry-dotnet is 70.0%, based on public PR activity from non-core contributors.
getsentry/sentry-dotnet currently has 5 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Balanced & professional review environment in getsentry/sentry-dotnet. 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/getsentry/sentry-dotnet?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 22:00 UTC (22:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 21:00 to 01:00 UTC (21:00 - 01:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~40 hours (88% approval). Large PRs (>500 lines) take ~295 hours (32% approval). Keep your diff compact for rapid review.
Background CodeQL recently started failing on main and every branch with: Loaded a configuration file for version '4.37.1', but running version '4.37.0' Dependabot treats each uses: line as a separate dependency, so it bumped github/codeql-action/init to v4.37.1 while leaving github/codeql-action/analyze on v4.37.0. CodeQL requires all of its action steps to run the same version, so analyze failed. The immediate skew was fixed in 4216c80 (aligning analyze to v4.37.1), landed opportunistically on PR #5414 to get CI green without stacking a separate PR — see #5414 (comment). Problem That was a manual patch. Nothing prevents the same drift from recurring the next time one codeql-action sub-action is bumped ahead of the other. Proposed fix Add a Dependabot group to the existing github-actions ecosystem in .github/dependabot.yml so all github/codeql-action/* sub-actions are always bumped together in a single atomic PR: - package-ecosystem: "github-actions" directories: - "/" -
Follow-up to #5381, as suggested by @bruno-garcia in this review: LGTM, I'd add some integration tests too as a follow up #5381 fixed a per-request resource leak (#5378) where SentryMiddleware created a new TaskBlockingListener (an EventListener that registers itself process-globally) on every request. The fix registers BlockingMonitor and TaskBlockingListener as singletons that the transient middleware resolves from DI. That PR includes a unit-level regression test (Constructor_CaptureBlockingCalls_SharesSingleListenerAcrossInstances), but we should also cover CaptureBlockingCalls with integration tests that exercise a real ASP.NET Core pipeline (e.g. via TestServer/WebApplicationFactory), for example: Multiple requests to an app with CaptureBlockingCalls = true result in exactly one TaskBlockingListener for the lifetime of the host (the #5378 leak scenario). A blocking call (e.g. Task.Delay(...).Wait()) inside a request produces the expected blocking-call event/log via the real Tp
Summary List both the Android Native Options and the Apple Native Options in the docs for the Sentry MAUI SDK, for easier discoverability. Remarks .NET for Android has the page Android Native Options: https://docs.sentry.io/platforms/dotnet/guides/android/configuration/native-options/ .NET for iOS, macOS, or Mac Catalyst has the page Apple Native Options: https://docs.sentry.io/platforms/dotnet/guides/apple/configuration/native-options/ MAUI has neither For discoverability, we could add both pages to the MAUI platform / guide.
Summary Creating a new issue via GitHub offers two "Blank Issues", that are reserved for maintainers. We should be able to remove one.
Description We don't have sentry-dotnet (nor MAUI) documentation for CrashedLastRun and OnCrashedLastRun. Related #4048 #4529
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 getsentry/sentry-dotnet, 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 getsentry/sentry-dotnet acknowledge new external contributions in approximately 2 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 70.0% were successfully merged into the primary branch.
getsentry/sentry-dotnet has a recorded first-timer success rate of 71.4%. 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 60.1 places getsentry/sentry-dotnet in the Welcoming tier.
The external pull request merge rate is 70.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, getsentry/sentry-dotnet currently has 5 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for getsentry/sentry-dotnet 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.