1.5.0 (current)
From divviup/libprio-rs. Audited without comment by David Cook.
These reviews are from cargo-vet. To add your review, set up cargo-vet
and submit your URL to its registry.
1.5.0 (current)
From divviup/libprio-rs. Audited without comment by David Cook.
1.5.0 (current)
From google/supply-chain copy of chromium. Audited without comment by ChromeOS.
1.5.0 (current)
From kornelski/crev-proofs copy of git.savannah.gnu.org.
cargo-vet does not verify reviewers' identity. You have to fully trust the source the audits are from.
This crate can be compiled, run, and tested on a local workstation or in controlled automation without surprising consequences. More…
Inspection reveals that the crate in question does not attempt to implement any cryptographic algorithms on its own.
Note that certification of this does not require an expert on all forms of cryptography: it's expected for crates we import to be "good enough" citizens, so they'll at least be forthcoming if they try to implement something cryptographic. When in doubt, please ask an expert.
All crypto algorithms in this crate have been reviewed by a relevant expert.
Note: If a crate does not implement crypto, use does-not-implement-crypto
,
which implies crypto-safe
, but does not require expert review in order to
audit for.
May have been packaged automatically without a review
This review is from Crev, a distributed system for code reviews. To add your review, set up cargo-crev
.
The current version of assert_matches is 1.5.0.
1.3.0 (older version) Thoroughness: Medium Understanding: Medium
by zoechi on 2019-11-04
Simple but useful with tests and docs.
Lib.rs has been able to verify that all files in the crate's tarball are in the crate's repository. Please note that this check is still in beta, and absence of this confirmation does not mean that the files don't match.
Crates in the crates.io registry are tarball snapshots uploaded by crates' publishers. The registry is not using crates' git repositories, so there is a possibility that published crates have a misleading repository URL, or contain different code from the code in the repository.
To review the actual code of the crate, it's best to use cargo crev open assert_matches
. Alternatively, you can download the tarball of assert_matches v1.5.0 or view the source online.
Packaged for Guix (crates-io)