0.10.6 — diff review from 0.10.5 only (older version)
From bytecodealliance/wasmtime. By Andrew Brown.
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 SHA-1 is 0.11.0-pre.4.
0.10.6 — diff review from 0.10.5 only (older version)
From bytecodealliance/wasmtime. By Andrew Brown.
0.10.6 (older version)
From kornelski/crev-proofs copy of salsa.debian.org.
Only in debcargo (unstable). Changelog:
0.10.6 (older version)
From kornelski/crev-proofs copy of git.savannah.gnu.org.
Packaged for Guix (crates-crypto)
0.10.5 (older version)
From mozilla/supply-chain copy of hg. Audited without comment by Dana Keeler.
0.10.5 — diff review from 0.10.0 only (older version)
From mozilla/supply-chain copy of hg. Audited without comment by Mike Hommey.
0.10.5 (older version)
From google/supply-chain copy of fuchsia. By David Koloski.
Reviewed on https://fxrev.dev/712371.
cargo-vet does not verify reviewers' identity. You have to fully trust the source the audits are from.
This crate will not introduce a serious security vulnerability to production software exposed to untrusted input. More…
This crate can be compiled, run, and tested on a local workstation or in controlled automation without surprising consequences. More…
Excellent soundness.
Full description of the audit criteria can be found at https://github.com/google/rust-crate-audits/blob/main/auditing_standards.md#ub-risk-1
Negligible unsoundness or average soundness.
Full description of the audit criteria can be found at https://github.com/google/rust-crate-audits/blob/main/auditing_standards.md#ub-risk-2
Mild unsoundness or suboptimal soundness.
Full description of the audit criteria can be found at https://github.com/google/rust-crate-audits/blob/main/auditing_standards.md#ub-risk-3
Extreme unsoundness.
Full description of the audit criteria can be found at https://github.com/google/rust-crate-audits/blob/main/auditing_standards.md#ub-risk-4
May have been packaged automatically without a review
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 sha1
. Alternatively, you can download the tarball of sha1 v0.11.0-pre.4 or view the source online.
Only new code is some loongarch64 additions which include assembly code for that platform.