GideonBear Name: crates.io Homepage: https://crates.io Short description: The Rust community’s crate registry Optional API documentation URL: https://doc.rust-lang.org/cargo/reference/registries.html https://github.com/theduke/crates-io-api
vladimyr GideonBear API documentation you've linked to is actually a subset of crates.io API used by cargo tool as stated here: https://crates.io/data-access#api Looking into crates.io registry source code reveals /api/v1/users/{user} route: https://github.com/rust-lang/crates.io/blob/0d9b66a/src/controllers/user/other.rs#L29 That route handler will then use diesel ORM to fetch requested user from the database (https://github.com/rust-lang/crates.io/blob/0d9b66a/crates/crates_io_database/src/models/user.rs#L17) and pass it through API view (https://github.com/rust-lang/crates.io/blob/0d9b66a/src/views.rs#L746-L789) before forming final API response. If you take a closer look, you'll quickly realize that the registry doesn't actually store any user data besides user's GitHub username, avatar URL and optional display name, so there is no place to put Keyoxide proof into.
GideonBear @vladimyr is proving the GitHub account linked to the crates.io account enough to prove the crates.io account?
GideonBear Which you can link to a crates.io username via https://crates.io/api/v1/crates/<crate_name>/owner_user (example: https://crates.io/api/v1/crates/jetbrains_toolbox_updater/owner_user)