Rust Cargo.toml Health Checker — Find Outdated and Yanked Crates
Paste your Cargo.toml. Checks every [dependencies] and [dev-dependencies] entry against crates.io for the latest version, yanked status, total downloads, and last update date.
Paste your Cargo.toml. Checks each dependency against crates.io for the latest version, yanked status, and last update date. Covers both [dependencies] and [dev-dependencies].
What to watch for
- Yanked versions: The crate maintainer explicitly pulled a version (usually due to a critical bug or security issue). Cargo won’t install a yanked version for new projects, but existing
Cargo.lockpins can still reference yanked versions. - Major version behind: Rust crates use strict semver.
reqwest = "0.11"→ v0.12 means the API changed and you’ll need to update your code, not just the version number. Check the crate’s CHANGELOG before upgrading. - Version ranges in Cargo.toml:
= "1.28"in Cargo.toml is actually^1.28(semver-compatible). This checker shows the latest crates.io version — your actual installed version may be newer within that range. Checkcargo outdatedfor precise Cargo.lock analysis. - Download counts: Very low download counts on production deps can indicate abandoned crates. 100M+ means battle-tested (tokio, serde). Under 10K might warrant a closer look at maintenance status.
For CVE scanning, use the Vulnerability Scanner. Full dependency health suite: npm · PyPI · Go · Rust (this tool).
Founded
2023 in London, UK
Contact
hello@releaserun.com