The Rust toolchain installer
C-Rank Grade: A (Welcoming) - 65/100
External PR Merge Rate: 52%
Response Time: -
First Timer Success: 67%
rust-lang/rustup has a recorded first-timer success rate of 66.7%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in rust-lang/rustup 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 65.5 places rust-lang/rustup in the A tier.
The external contributor pull request merge rate for rust-lang/rustup is 52.2%, based on public PR activity from non-core contributors.
rust-lang/rustup currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Established Rust ecosystem in rust-lang/rustup. Maintains structured code review standards for external contributors.
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/rust-lang/rustup?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 09:00 UTC (09:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 08:00 to 12:00 UTC (08:00 - 12:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (65% approval). Large PRs (>500 lines) take ~115 hours (23% approval). Keep your diff compact for rapid review.
Similar to the case in #4164: rustup update fails (unrelated to issue) rustup target remove wasm32-wasi fails rustup +target remove wasm32-wasi succeeds, as the default toolchain was nightly as specified in .rustup/settings.toml ... however the related error kind is RustupError::UnknownComponents which would be emitted during both rustup component add and rustup component rm (instead of the rustup target rm command shown above): rustup/src/errors.rs Lines 141 to 145 in 2919b80 #[error("{}", unknown_components_msg(.desc, .components))] UnknownComponents { desc: ToolchainDesc, components: Vec<UnknownComponentInfo>, }, ... so we should be smarter in terms of suggestions. Or, as a simplification, if
rustup to provide a way to list toolchains without human "hints" Greetings from fish-shell. The fish command line shell ships tab-completions for rustup. A user might type rustup --toolchain <TAB> and expect the toolchains to be offered as completions; fish-shell invokes rustup toolchain list to discover these options. But this recent rustup change causes rustup to print a "setup hint" to stdout if no toolchains are installed. This setup hint emits the text "no installed toolchains," which is difficult to disambiguate from a real toolchain (in practice our shoddy regex computes "no" as a toolchain). We discovered this through test failures that we have worked around. We don't expect this to affect many users, since rustup users overwhelmingly have at least one rust toolchain installed. Still I think this is worth surfacing, and fixing. Solution you'd like This request is for a machine-friendly way to determine installed toolchains without unwanted "hint" stdout intended for humans. I t
Problem you are trying to solve I'd like to run rustup update stable and get an indication of whether stable actually updated, without parsing rustup's human-readable output. Solution you'd like I'd like to have an option to have rustup update set an exit code based on whether any of the requested toolchains had an update. (This shouldn't be the default, since that might cause workflows to fail when a no-op update occurs.) Notes No response
Problem you are trying to solve the docs still state that VS 2022 is the latest version: rustup/doc/user-guide/src/installation/windows-msvc.md Line 57 in 9a342e3 Rust supports Visual Studio 2017 and later but it is recommended that you use the latest version (currently 2022) for new projects. however, VS 2026 has been out for a while now (since november 2025) i couldn't find any info anywhere on the rust website about the compatibility of rust & VS 2026 (and, admittedly, didn't try it yet - i have VS 2022 installed, after all) Solution you'd like the docs are updated for VS 2026. either everything already works with VS 2026, then it's probably enough to just swap out 2022 for 2026 everywhere, otherwise a comment should be added with a link to a tracking issue for full VS 2026 support (though i didn't find any such issue) Notes No response
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 rust-lang/rustup, 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 rust-lang/rustup acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 52.2% were successfully merged into the primary branch.
rust-lang/rustup has a recorded first-timer success rate of 66.7%. Repositories ranked Welcoming 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 65.5 places rust-lang/rustup in the Welcoming tier.
The external pull request merge rate is 52.2%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, rust-lang/rustup 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 rust-lang/rustup 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.