C-Rank Grade: A (Welcoming) - 60/100
External PR Merge Rate: 86%
Response Time: 3d
First Timer Success: 100%
dotnet/install-scripts has a recorded first-timer success rate of 100.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in dotnet/install-scripts respond to incoming external pull requests in approximately 69.1 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 59.9 places dotnet/install-scripts in the A tier.
The external contributor pull request merge rate for dotnet/install-scripts is 86.4%, based on public PR activity from non-core contributors.
dotnet/install-scripts currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Open-source repository analyzed with precision C-Rank telemetry.
Collaborative maintainer environment in dotnet/install-scripts. Reviews community pull requests with focus on project quality.
Discussions in dotnet/install-scripts 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/dotnet/install-scripts?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 15:00 UTC (15:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 15:00 to 19:00 UTC (15:00 - 19:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~45 hours (96% approval). Large PRs (>500 lines) take ~332 hours (39% approval). Keep your diff compact for rapid review.
When a one-part channel (e.g. -c 10) is specified for dotnet-install.sh, the script attempts to resolve it and fails with unclear messaging. The output currently attempts to download files for the one-part channel, leading to a confusing 404 error. The script help text specifies that channels must be 'STS', 'LTS', a two-part version (A.B), or a three-part SDK band (A.B.Cxx), but this expectation isn't reflected in the error message. Request: Detect if a one-part channel is given and update the output to indicate it is not valid. Make the error message clear about supported channel formats and provide a suggested workaround (e.g. use -c 10.0). This will help users avoid confusion and parallels a similar situation described in issue #685 (and previously #461). Repro: bash dotnet-install.sh -c 10 --verbose # output is unclear, attempted downloads fail with 404 Expected: Clear error about channel format and workaround.
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 dotnet/install-scripts, 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 dotnet/install-scripts acknowledge new external contributions in approximately 2 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 86.4% were successfully merged into the primary branch.
dotnet/install-scripts has a recorded first-timer success rate of 100.0%. 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 59.9 places dotnet/install-scripts in the Welcoming tier.
The external pull request merge rate is 86.4%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, dotnet/install-scripts currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for dotnet/install-scripts 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.