#cargo-subcommand #linter

bin+lib cargo-deadlinks

Cargo subcommand for checking your documentation for broken links

16 releases

0.8.1 Oct 13, 2021
0.8.0 Jan 18, 2021
0.7.2 Jan 9, 2021
0.7.1 Dec 18, 2020
0.1.0 Mar 25, 2016

#265 in Cargo plugins

Download history 132/week @ 2023-06-08 92/week @ 2023-06-15 211/week @ 2023-06-22 196/week @ 2023-06-29 143/week @ 2023-07-06 131/week @ 2023-07-13 260/week @ 2023-07-20 180/week @ 2023-07-27 110/week @ 2023-08-03 126/week @ 2023-08-10 108/week @ 2023-08-17 272/week @ 2023-08-24 218/week @ 2023-08-31 221/week @ 2023-09-07 151/week @ 2023-09-14 175/week @ 2023-09-21

785 downloads per month
Used in gluon_doc



cargo-deadlinks • Crates.io License

Check your cargo doc documentation for broken links!

Useful if you just refactored the structure of your crate or want to ensure that your documentation is readable offline.

This crate pairs well with intra-doc links and cargo-intraconv, which make it easier to write links without having to know the exact HTML page rustdoc will generate.

deadlinks can also be used on projects that aren't Rust crates.


Install cargo-deadlinks via:

cargo install cargo-deadlinks

Alternatively, install pre-built binaries from the releases page.


From your packages directory run:

# this will automatically run `cargo doc` for you
# any broken links will show up in the output
cargo deadlinks
# if you also want to check http and https links
cargo deadlinks --check-http

By default cargo deadlinks will check only the offline (file://) links of your package.

If you want to check the documentation in another directory e.g. to check all your dependencies, you can provide the --dir argument:

cargo deadlinks --dir target/doc

To check a project that isn't a crate, use deadlinks instead:

# this requires that you already have a static site in build/html
deadlinks build/html

For information about other arguments run cargo deadlinks --help.

Minimum Supported Rust Version (MSRV)

The current MSRV is 1.45.0. This may be increased in minor versions, but will never increase in a patch version.


We are happy about any contributions!

To get started you can take a look at our Github issues.

Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as below, without any additional terms or conditions.


Licensed under either of

at your option.


~586K SLoC