* (all versions)
From zcash/rust-ecosystem copy of zcash/librustzcash. Trusted without checking without comment by on 2022-05-10.
These reviews are from cargo-vet. To add your review, set up cargo-vet and submit your URL to its registry.
* (all versions)
From zcash/rust-ecosystem copy of zcash/zcash. Trusted without checking without comment by on 2022-05-10.
cargo-vet does not verify reviewers' identity. You have to fully trust the source the audits are from.
- safe-to-deploy (implies safe-to-run)
-
This crate will not introduce a serious security vulnerability to production software exposed to untrusted input. More…
- safe-to-run
Implied by other criteria
This crate can be compiled, run, and tested on a local workstation or in controlled automation without surprising consequences. More…
- crypto-reviewed
-
The cryptographic code in this crate has been reviewed for correctness by a member of a designated set of cryptography experts within the project.
Lib.rs has been able to verify that all files in the crate's tarball, except Cargo.lock,
are in the crate's repository with a git tag matching the version. 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 halo2_proofs. Alternatively, you can download the tarball of halo2_proofs v0.3.0 or view the source online.