This site is being rebuilt and some pages are out of date. For current details, write to [email protected]. This notice goes away when the rebuild is done.

No analytics unless you allow it, no tracking. This site keeps in your browser the language you pick, the theme, its colour, which site you chose, the currency on the pricing page and that you closed this notice; signing in adds session cookies. The legal page has the details.

Sign in

Radar · Rust · Archive · Week 22 · May 25 – 31, 2026

Crates.io Username Concept Introduced

Worth knowingtooling

What changed
The RFC proposes a separate crates.io username from GitHub or other OAuth providers to support multiple OAuth providers and handle username collisions.
Production impact
The source does not say.
Try it
Read the RFC text at https://github.com/rust-lang/rfcs/blob/master/text/3946-crates-io-username-identity.md.
Source
github.com/rust-lang/rfcs/pull/3963

Understand it, then run it

Run it now

Todayrust
// This program demonstrates the problem that the new crates.io username concept
// solves: two users with the same GitHub name cannot both use that name on crates.io.
// Since the change is not yet in the current Rust release, we simply illustrate
// the issue with a mock example.

fn main() {
    // Two users with the same GitHub username "alice"
    let github_user_a = "alice";
    let github_user_b = "alice";

    // On crates.io before the change, both would collide
    if github_user_a == github_user_b {
        println!("Collision: both users would have the same crates.io name.");
    } else {
        println!("No collision.");
    }

    // After the change, each can choose a distinct crates.io username
    let crates_io_username_a = "alice_dev";
    let crates_io_username_b = "alice_prod";

    if crates_io_username_a != crates_io_username_b {
        println!("No collision after username decoupling: {} vs {}", crates_io_username_a, crates_io_username_b);
    }
}

What it printed when we ran it on Rust 1.98.1 (edition 2024)

Collision: both users would have the same crates.io name.
No collision after username decoupling: alice_dev vs alice_prod

Run sends this program (for Solidity, the contract and its tests) to our own sandbox, where it is compiled and run once, with no network, and what it printed or the test report comes back here. Nothing is kept. Runs are counted per visitor for the day so everyone gets a turn; the details are on the legal page.

Written by gpt-oss-20b from the linked source · claims checked against the sources · archive, not individually reviewed