-
Notifications
You must be signed in to change notification settings - Fork 3
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
document auditing Rust crates via Cargo Vet
- Loading branch information
Showing
1 changed file
with
23 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -196,3 +196,26 @@ diff review for ``cryptography`` 2.3 to 2.7: | |
6. Comment on the PR indicating that the diff review is approved. | ||
|
||
7. Send the same content from the wiki to [email protected]. | ||
|
||
|
||
Auditing Rust dependencies | ||
-------------------------- | ||
We audit Rust crates using the `Cargo Vet <https://mozilla.github.io/cargo-vet/index.html>`_ tool. To get started: | ||
|
||
.. code:: | ||
$ cargo install --locked cargo-vet | ||
Then you can audit both new and updated crates: | ||
|
||
.. code:: | ||
$ cargo vet diff $CRATE $OLD $NEW # $CRATE has been updated from $OLD to $NEW. | ||
$ cargo vet inspect $CRATE $VERSION # $CRATE is entirely new at $VERSION. | ||
[...] | ||
$ cargo vet certify | ||
Consult `Cargo Vet's policy documentation | ||
<https://mozilla.github.io/cargo-vet/specifying-policies.html>`_ on | ||
the difference between auditing a given crate as `safe-to-deploy` | ||
versus `safe-to-run`. |