Distributed transaction solution in micro-service base on eventually consistency, also an eventbus with Outbox pattern
C-Rank Grade: D (Risky) - 8/100
External PR Merge Rate: -
Response Time: -
First Timer Success: -
dotnetcore/CAP has a recorded first-timer success rate of 0.0%. Repositories ranked D typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in dotnetcore/CAP 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 7.5 places dotnetcore/CAP in the D tier.
The external contributor pull request merge rate for dotnetcore/CAP is 0.0%, based on public PR activity from non-core contributors.
dotnetcore/CAP does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
Collaborative maintainer environment in dotnetcore/CAP. Reviews community pull requests with focus on project quality.
Discussions in dotnetcore/CAP 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/dotnetcore/CAP?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
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (81% approval). Large PRs (>500 lines) take ~115 hours (29% approval). Keep your diff compact for rapid review.
Summary Kafka: message committed without executing subscriber during shutdown, then replayed out of order after FallbackWindowLookbackSeconds Steps to Reproduce During a rolling restart, a received message can be committed to Kafka without its subscriber ever running. The row stays in Scheduled state and is only picked up by the retry processor after FallbackWindowLookbackSeconds. The result is a message on a single partition executing minutes after a higher-offset message from the same partition, with Retries = 0 and no warning or error in the logs. I understand CAP is at-least-once and does not promise partition ordering after a subscriber failure. This report is about a case where no failure happened and no subscriber code ran: the dispatcher refused the message because CAP was stopping, the caller could not see that, and it committed the offset anyway. The shutdown path that should have prevented this waits on a task that is always already completed. Environment DotNetCore.CAP 10.
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 dotnetcore/CAP, 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 dotnetcore/CAP acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 0.0% were successfully merged into the primary branch.
dotnetcore/CAP has a recorded first-timer success rate of 0.0%. Repositories ranked Risky 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 7.5 places dotnetcore/CAP in the Risky tier.
The external pull request merge rate is 0.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
dotnetcore/CAP does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.
All metrics displayed for dotnetcore/CAP 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.