diff --git a/posts/2016-05-16-rust-at-one-year.md b/posts/2016-05-16-rust-at-one-year.md index 42ce18d1d..caea83d05 100644 --- a/posts/2016-05-16-rust-at-one-year.md +++ b/posts/2016-05-16-rust-at-one-year.md @@ -20,7 +20,7 @@ having fun doing it. And yesterday, Rust turned one year old. - + ### Rust in numbers diff --git a/posts/inside-rust/2019-10-03-Keeping-secure-with-cargo-audit-0.9.md b/posts/inside-rust/2019-10-03-Keeping-secure-with-cargo-audit-0.9.md index 14eba2c1a..e5f0ca83b 100644 --- a/posts/inside-rust/2019-10-03-Keeping-secure-with-cargo-audit-0.9.md +++ b/posts/inside-rust/2019-10-03-Keeping-secure-with-cargo-audit-0.9.md @@ -27,7 +27,7 @@ Previously, when `cargo-audit` found a vulnerability in a project, it would disp The latest release prints an inverse dependency tree (ala the excellent [cargo-tree](https://github.com/sfackler/cargo-tree) crate) for each advisory showing how a vulnerable dependency is included in your project: -![cargo audit with dependency tree](https://raw.githubusercontent.com/RustSec/cargo-audit/a840f7b/screenshot.png) +![cargo audit with dependency tree](/images/inside-rust/2019-10-03-Keeping-secure-with-cargo-audio-0.9/cargo-audit-dependency-tree.png) In future versions of `cargo-audit` we [hope to add a `cargo audit fix` command](https://github.com/RustSec/cargo-audit/issues/23) ala `npm audit fix` which can either automatically update the necessary dependencies or provide instructions on how to do so. If that feature interests you and you'd like to contribute, [we're looking for help](https://github.com/RustSec/cargo-audit/issues/23)! diff --git a/posts/inside-rust/2020-01-23-Introducing-cargo-audit-fix-and-more.md b/posts/inside-rust/2020-01-23-Introducing-cargo-audit-fix-and-more.md index b1148f6be..3d22977a0 100644 --- a/posts/inside-rust/2020-01-23-Introducing-cargo-audit-fix-and-more.md +++ b/posts/inside-rust/2020-01-23-Introducing-cargo-audit-fix-and-more.md @@ -22,7 +22,7 @@ $ cargo install cargo-audit --features=fix This will perform the same audit process as `cargo audit` initially, and then attempt to apply fixes to your `Cargo.toml`: -![cargo audit fix screenshot](https://raw.githubusercontent.com/RustSec/cargo-audit/c857beb/img/screenshot-fix.png) +![cargo audit fix screenshot](/images/inside-rust/2020-01-23-Introducing-cargo-audit-fix-and-more/cargo-audit-fix.png) Under the hood, it uses [cargo-edit](https://github.com/killercup/cargo-edit) (as a library) to perform modifications to your `Cargo.toml` file, using the fixed version requirements listed in the advisory to try to perform an automatic upgrade to a non-vulnerable version of a dependency for each advisory. diff --git a/static/images/2016-05-16-rust-at-one-year/cupcakes.jpg b/static/images/2016-05-16-rust-at-one-year/cupcakes.jpg new file mode 100644 index 000000000..fde644d9b Binary files /dev/null and b/static/images/2016-05-16-rust-at-one-year/cupcakes.jpg differ diff --git a/static/images/inside-rust/2019-10-03-Keeping-secure-with-cargo-audio-0.9/cargo-audit-dependency-tree.png b/static/images/inside-rust/2019-10-03-Keeping-secure-with-cargo-audio-0.9/cargo-audit-dependency-tree.png new file mode 100644 index 000000000..8fd8800d2 Binary files /dev/null and b/static/images/inside-rust/2019-10-03-Keeping-secure-with-cargo-audio-0.9/cargo-audit-dependency-tree.png differ diff --git a/static/images/inside-rust/2020-01-23-Introducing-cargo-audit-fix-and-more/cargo-audit-fix.png b/static/images/inside-rust/2020-01-23-Introducing-cargo-audit-fix-and-more/cargo-audit-fix.png new file mode 100644 index 000000000..ea1c17e29 Binary files /dev/null and b/static/images/inside-rust/2020-01-23-Introducing-cargo-audit-fix-and-more/cargo-audit-fix.png differ