Another six months have passed since our since then.
Untangling crates.io Accounts from GitHub
At the end of May, the crates.io team accepted
Advisories and Suggestions
In our database. We have since taken this integration one step further: crates that RustSec has flagged as unmaintained now show a warning banner directly on their crate pages, linking to the corresponding advisory for details and possible alternatives. Thanks to repository, together with a documented inclusion policy: standard library replacements only, every entry must cite the stable std, core, or alloc API and Rust version, and crate maintainers get a notice-and-comment window before an entry is added. New entries can be proposed upstream and can benefit other tools too.
Svelte Frontend Migration Completed
In our . This experiment has concluded successfully: the new frontend reached feature parity, went through a for a framework that served crates.io well for many years, and the Svelte team for making the transition so enjoyable.
document got a complete rewrite. It is now organized around the high-level systems that make up crates.io and how they fit together, and includes walkthroughs of what happens when you run cargo publish, why a typical crate download never touches our API servers, and how download counts are derived from CDN access logs.
Definition lists: READMEs now render Markdown already supported them, the extension just wasn't enabled yet. Thanks to
Feedback
We hope you enjoyed this update on the development of crates.io. If you have any feedback or questions, please let us know on . We are always happy to hear from you and are looking forward to your feedback!
SOCIAL SHARE CARD GENERATOR