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

0.14.3 (current) unknown

From kornelski/crev-proofs copy of salsa.debian.org.

Only in debcargo (experimental). Changelog:

  • Team upload.
  • Package hashbrown 0.14.3 from crates.io using debcargo 2.6.1
  • Disable nightly features.
  • Disable rkyv feature due to dependency cycle.

The current version of hashbrown is 0.14.3.

0.14.0 — diff review from 0.13.2 only (older version) safe-to-deploy

From zcash/rust-ecosystem copy of zcash/zcash. By Daira Emma Hopwood.

There is some additional use of unsafe code but the changes in this crate looked plausible. There is a new default dependency on the allocator-api2 crate, which itself has quite a lot of unsafe code. Many previously undocumented safety requirements have been documented.

0.13.2 — diff review from 0.13.1 only (older version) safe-to-deploy

From bytecodealliance/wasmtime. By Trevor Elliott.

I read through the diff between v0.13.1 and v0.13.2, and verified that the changes made matched up with the changelog entries. There were very few changes between these two releases, and it was easy to verify what they did.

0.13.1 — diff review from 0.12.3 only (older version) safe-to-deploy

From bytecodealliance/wasmtime. By Chris Fallin.

The diff looks plausible. Much of it is low-level memory-layout code and I can't be 100% certain without a deeper dive into the implementation logic, but nothing looks actively malicious.

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

This crate can be compiled, run, and tested on a local workstation or in controlled automation without surprising consequences. More…

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 implies crypto-safe, but does not require expert review in order to audit for.

unknown

May have been packaged automatically without a review


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

The current version of hashbrown is 0.14.3.

0.9.1 (older version) Rating: Positive Thoroughness: Low Understanding: Low

by niklasf on 2021-01-01

A high quality crate that is now used by the standard library. Some use cases for using it directly remain, such as no_std support, and low level APIs for building other datastructures.

0.8.2 (older version) Rating: Positive Thoroughness: Low Understanding: Low

Approved without comment by kornelski on 2020-08-18


Lib.rs has been able to verify that all files in the crate's tarball 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 hashbrown. Alternatively, you can download the tarball of hashbrown v0.14.3 or view the source online.