C# Dev Tools: A comprehensive VS Code extension that provides Solution Explorer functionality for .NET projects with file template support and code analysis features.
C-Rank Grade: C (Moderate) - 38/100
External PR Merge Rate: -
Response Time: -
First Timer Success: -
jakubkozera/vsc-csharp-dev-tools has a recorded first-timer success rate of 0.0%. Repositories ranked C typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in jakubkozera/vsc-csharp-dev-tools 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 38.0 places jakubkozera/vsc-csharp-dev-tools in the C tier.
The external contributor pull request merge rate for jakubkozera/vsc-csharp-dev-tools is 0.0%, based on public PR activity from non-core contributors.
jakubkozera/vsc-csharp-dev-tools does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
Active maintainer team in jakubkozera/vsc-csharp-dev-tools welcoming community pull requests and bug fixes.
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/jakubkozera/vsc-csharp-dev-tools?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.
Description The issue Often when I type into the code window, it opens a input dropdown where the command palette is. The dropdown says "No active cleanup profile" prompt. This issue happens every 1 to 3 keys that I press. How I know this extension is the problem I ran "Help: Start Extension Bisect" Steps to Reproduce Open any .cs file Click somewhere in the code window to start typing Press a few letter keys, between 1 to 3 is enough, Expected Behavior I expect to be able to type letters using key presses without opening anything. Actual Behavior Opens a drop down after a few keypresses. Extension Version 1.10.15 VS Code Instance VS Code Operating System ArchLinux .NET Version .NET 10.0.111 SDK Run Mode None MTP Enabled? (if testing-related) None C# Dev Tools Output No output Additional Context
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 jakubkozera/vsc-csharp-dev-tools, 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 jakubkozera/vsc-csharp-dev-tools 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.
jakubkozera/vsc-csharp-dev-tools has a recorded first-timer success rate of 0.0%. Repositories ranked Moderate 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 38.0 places jakubkozera/vsc-csharp-dev-tools in the Moderate 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.
jakubkozera/vsc-csharp-dev-tools 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 jakubkozera/vsc-csharp-dev-tools 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.