This MSBuild SDK is designed to allow for the easy creation and use of SDK (shortform) projects targeting ASP.NET 4.x using System.Web.
C-Rank Grade: D (Risky) - 8/100
External PR Merge Rate: -
Response Time: -
First Timer Success: -
CZEMacLeod/MSBuild.SDK.SystemWeb 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 CZEMacLeod/MSBuild.SDK.SystemWeb 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 8.0 places CZEMacLeod/MSBuild.SDK.SystemWeb in the D tier.
The external contributor pull request merge rate for CZEMacLeod/MSBuild.SDK.SystemWeb is 0.0%, based on public PR activity from non-core contributors.
CZEMacLeod/MSBuild.SDK.SystemWeb currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
This MSBuild SDK is designed to allow for the easy creation and use of SDK (shortform) projects targeting ASP.NET 4.x using System.Web.
Collaborative maintainer environment in CZEMacLeod/MSBuild.SDK.SystemWeb. Reviews community pull requests with focus on project quality.
Discussions in CZEMacLeod/MSBuild.SDK.SystemWeb 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/CZEMacLeod/MSBuild.SDK.SystemWeb?utm_source=github&utm_medium=badge)
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.
See #69 (comment) #106 (comment) A list of all the possible error/warning messages with ID's should be added to the Wiki and/or docs and all the messages updated to include error numbers. This issue is here to track the progress of implementing this.
Issue Currently WebApplicationsTargetPath depends on a locally installed version of visual studio - either buildtools or any full version such as community or professional with the appropriate workload installed. Using tools such as dotnet build or dotnet test are more difficult as they require either resolving the location of VS using VSWhere or passing in an empty targets file. Solutions Set the default action that if there is no resolved targets file available that a warning is emitted but no failure occurs. Add a mechanism to resolve the file (assuming VS is installed) without external scripts/actions or setting env variables etc. Include the required tasks and targets directly in the SDK. Use a packaged version of the required tasks and targets. Either of 3 or 4 is preferred as this makes the solution robust and maintainable. It also obviates the need for additional installations. The best solution would be for Microsoft to release an official package, probably versioned to matc
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 CZEMacLeod/MSBuild.SDK.SystemWeb, 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 CZEMacLeod/MSBuild.SDK.SystemWeb 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.
CZEMacLeod/MSBuild.SDK.SystemWeb 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 8.0 places CZEMacLeod/MSBuild.SDK.SystemWeb 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.
Yes, CZEMacLeod/MSBuild.SDK.SystemWeb 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 CZEMacLeod/MSBuild.SDK.SystemWeb 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.