Code reviews of the Failure crate // Lib.rs

RUSTSEC-2020-0036 (unmaintained) on 2020-05-02: failure is officially deprecated/unmaintained

The failure crate is officially end-of-life: it has been marked as deprecated by the former maintainer, who has announced that there will be no updates or maintenance work on it going forward.

The following are some suggested actively developed alternatives to switch to:

RUSTSEC-2019-0036 (unsound) on 2019-11-13: Type confusion if __private_get_type_id__ is overridden

Safe Rust code can implement malfunctioning __private_get_type_id__ and cause type confusion when downcasting, which is an undefined behavior.

Users who derive Fail trait are not affected.

This review is from cargo-vet. To add your review, set up cargo-vet and submit your URL to its registry.

The current version of Failure is 0.1.8.

0.1.7 (older version) safe-to-run

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

Packaged for Debian (oldstable). Changelog:

Package failure 0.1.7 from crates.io using debcargo 2.4.2

cargo-vet does not verify reviewers' identity. You have to fully trust the source the audits are from.

safe-to-run

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

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

The current version of Failure is 0.1.8.

0.1.5 (older version) Rating: Positive Thoroughness: Low Understanding: Medium

Approved without comment by dpc on 2019-07-03

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