2.0.0 — diff review from 1.1.0 only (current)
From bytecodealliance/wasmtime. By Trevor Elliott.
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 rustc-hash is 2.0.0.
1.1.0 (older version)
From google/supply-chain copy of chromium. By George Burgess IV.
The hash this crate implements is explicitly non-cryptographic.
1.1.0 (older version)
From google/supply-chain copy of chromium. Audited without comment by Android Legacy.
1.1.0 (older version)
From mozilla/supply-chain copy of hg. By Bobby Holley.
Straightforward crate with no unsafe code, does what it says on the tin.
1.1.0 (older version)
From kornelski/crev-proofs copy of salsa.debian.org.
Packaged for Debian (stable). Changelog:
- Package rustc-hash 1.1.0 from crates.io using debcargo 2.4.3
1.1.0 (older version)
From kornelski/crev-proofs copy of git.savannah.gnu.org.
Packaged for Guix (crates-io)
cargo-vet does not verify reviewers' identity. You have to fully trust the source the audits are from.
- does-not-implement-crypto (implies crypto-safe)
-
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.
- crypto-safe
Implied by other criteria
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 impliescrypto-safe, but does not require expert review in order to audit for.- safe-to-run
-
This crate can be compiled, run, and tested on a local workstation or in controlled automation without surprising consequences. More…
- safe-to-deploy (implies safe-to-run)
-
This crate will not introduce a serious security vulnerability to production software exposed to untrusted input. More…
- unknown
-
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 rustc-hash. Alternatively, you can download the tarball of rustc-hash v2.0.0 or view the source online.
Chris Fallin reviewed this update with me, and we didn't find anything surprising. We did verify that the new constants did originate in the paper referenced.