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

0.5.6 (current) safe-to-run

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

Packaged for Debian (stable). Changelog:

  • Team upload.
  • Package linked-hash-map 0.5.6 from crates.io using debcargo 2.5.0
  • Drop no-clippy.patch, upstream Cargo.toml no longer mentions clippy.
  • Add patch to add tests that are included in upstream git but not included in the Crates.io release.

The current version of LinkedHashMap is 0.5.6.

0.5.4 (older version) safe-to-deploy

From mozilla/supply-chain copy of hg. By Aria Beingessner.

I own this crate (I am contain-rs) and 0.5.4 passes miri. This code is very old and used by lots of people, so I'm pretty confident in it, even though it's in maintenance-mode and missing some nice-to-have APIs.

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…

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 LinkedHashMap is 0.5.6.

0.5.4 (older version) Rating: Neutral + Unmaintained Thoroughness: Low Understanding: Low

by kornelski on 2021-08-23

There's a lot of unsafe pointer-juggling here for managing linked lists.

0.5.2 (older version) Rating: Neutral Thoroughness: Low Understanding: Low

by kornelski on 2019-11-23

Show review…

lots of raw pointer manipulation and use of mem::uninitialized()


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 linked-hash-map. Alternatively, you can download the tarball of linked-hash-map v0.5.6 or view the source online.