By language · Rust
Abandoned Rust crates looking for a new maintainer
Rust crates have no formal deprecated field on crates.io. The adoption signals are all GitHub-level — the adopt-me topic, the looking-for-maintainer badge, and the GitHub issues. The Rust ecosystem also uses cargo yank for soft-deprecation.
Published July 13, 2026 · ~3 min read
The short version
- crates.io has no deprecate field — use
cargo yankfor soft-deprecation, GitHub signals for handoff discovery. - Watch edition migrations: a 2015-edition crate is a bigger commitment than the same crate on 2021.
- The standard signal vocabulary is the GitHub
adopt-metopic +looking-for-maintainerbadge + a pinned issue. - For evaluation, lib.rs + deps.rs show reverse-dependency graphs and freshness scores.
How to find abandoned Rust crates
Same as the other languages — the BreakPoint feed filtered to Rust, the GitHub adopt-me topic filtered to Rust, and the lib.rs reverse-dependency view for any crate. Watch for crates where the last release is 12+ months ago, the GitHub issue response time is months, and the bus factor is 1.
If you maintain: cargo yank + GitHub signals
Run cargo yank --vers <version> to prevent new projects from depending on the crate while allowing existing dependents to keep using it. This is reversible — you can cargo yank --undo if you come back. Then add the GitHub adopt-me topic, the looking-for-maintainer shield, and a pinned "Seeking new maintainer" issue. Drop the project on BreakPoint for discovery. The Rust community is on /r/rust and users.rust-lang.org — a "this is a good Rust crate looking for a new maintainer" post will get traction if the crate is genuinely useful.