Code reviews of the Secp256k1 crate // Lib.rs

These reviews are from Crev, a distributed system for code reviews. To add your review, set up cargo-crev.

The current version of Secp256k1 is 0.30.0.

0.27.0 (older version) Rating: Positive Thoroughness: High Understanding: High

by tcharding on 2023-03-21

I attest that this version of the library is secure to the best of my knowledge, I am not a cryptographer.

0.25.0 (older version) Rating: Strong Positive Thoroughness: High Understanding: High

by tcharding on 2022-12-16

Show review…

I have worked on maintaining this crate for the last 12 months, I attest that this version of the library is secure to the best of my knowledge

These reviews are from cargo-vet. To add your review, set up cargo-vet and submit your URL to its registry.

The current version of Secp256k1 is 0.30.0.

0.27.0 — diff review from 0.26.0 only (older version) safe-to-deploy, crypto-reviewed

From zcash/rust-ecosystem copy of zcash/librustzcash. Audited without comment by str4d.

0.21.2 (older version) unknown

From kornelski/crev-proofs copy of git.savannah.gnu.org.

Packaged for Guix (crates-crypto)

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.

unknown

May have been packaged automatically without a review

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 secp256k1. Alternatively, you can download the tarball of secp256k1 v0.30.0 or view the source online.