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

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…

unknown

May have been packaged automatically without a review


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

The current version of new_debug_unreachable is 1.0.4.

1.0.3 (older version) Rating: Positive Thoroughness: Low Understanding: High

by gitlab.com/KonradBorowski on 2019-07-30

Always causes UB, but that's exactly what this crate is supposed to do and it properly requires unsafe.


Crates in the crates.io registry are tarball snapshots uploaded by crates' publishers. The registry is not using crates' git repositories. There is absolutely no guarantee that the repository URL declared by the crate belongs to the crate, or that the code in the repository is the code inside the published tarball. To review the actual code of the crate, it's best to use cargo crev open new_debug_unreachable. Alternatively, you can download the tarball of new_debug_unreachable v1.0.4 or view the source online.