Visual Studio Code
C-Rank Grade: S (Elite) - 69/100
External PR Merge Rate: 71%
Response Time: -
First Timer Success: 35%
microsoft/vscode has a recorded first-timer success rate of 35.4%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in microsoft/vscode 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 68.7 places microsoft/vscode in the S tier.
The external contributor pull request merge rate for microsoft/vscode is 71.0%, based on public PR activity from non-core contributors.
microsoft/vscode currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Strict review standards in microsoft/vscode. Ensure PR scope matches issue requirements closely before requesting review.
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/microsoft/vscode?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 Wednesday - Friday from 20:00 to 00:00 UTC (20:00 - 00:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (86% approval). Large PRs (>500 lines) take ~115 hours (31% approval). Keep your diff compact for rapid review.
When I move the terminal to right side and the progress content is long.
Does this issue occur when all extensions are disabled?: Yes (only had the repro extension enabled) VS Code Version: Version: 1.108.2 Commit: c9d77990917f3102ada88be140d28b038d1dd7c7 Date: 2026-01-21T13:52:09.270Z Electron: 39.2.7 ElectronBuildId: 12953945 Chromium: 142.0.7444.235 Node.js: 22.21.1 V8: 14.2.231.21-electron.0 OS: Darwin arm64 25.1.0 OS Version: macos Tahoe 26.1 (25B78) Steps to Reproduce: Steps to repro. clone https://github.com/sboult/vscode-image-copy-to-clipboard-webview/tree/master open project in vscode npm install press f5 to launch the dev extension host use CMD+SHIFT+P (command palette) and select "Show Image in Webview" when the webview comes up right click on image and select "Copy" You will notice no image is copied to the clipboard. However, if you highlight the image and then use the context menu to copy it will go into the clipboard.
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 microsoft/vscode, 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 microsoft/vscode acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 71.0% were successfully merged into the primary branch.
microsoft/vscode has a recorded first-timer success rate of 35.4%. Repositories ranked Elite 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 68.7 places microsoft/vscode in the Elite tier.
The external pull request merge rate is 71.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, microsoft/vscode currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for microsoft/vscode 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.