← Back to blog

Introducing rust-doctor

A unified code health scanner for Rust projects — what it does, why it exists, and how to get started.

Arthur Jean

Why rust-doctor?

The Rust ecosystem has excellent individual tools — clippy for lints, cargo-audit for CVEs, cargo-deny for licenses, cargo-machete for unused deps. But no single tool combines them into a unified health score with custom rules that go beyond what any individual tool catches.

rust-doctor fills that gap.

What it catches that clippy alone misses

  1. Hardcoded secrets in connection strings and API keys
  2. Blocking I/O inside async functions (e.g., std::fs::read in an async fn)
  3. block_on() inside async contexts that cause deadlocks
  4. Framework-specific anti-patterns for tokio, axum, and actix-web
  5. Dependency vulnerabilities via cargo-audit CVE scanning
  6. Unused dependencies wasting compile time

Get started

npx -y rust-doctor@latest .

That's it. One command, one score, actionable diagnostics.