Lib.rs

› Anyhow › Reviews

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 Anyhow is 1.0.101.

1.0.100 — diff review from 1.0.97 only (older version) safe-to-deploy

From zcash/rust-ecosystem copy of zcash/librustzcash. By Jack Grigg.

Changes to the build script are to enable reusing the probe file within the crate, enable more features on newer Rust versions, and catch more errors.

Most of the changes to unsafe code are refactors to surrounding safe code, and not actually altering the unsafe blocks. The new instances of unsafe are to allow errors to be converted to Box<dyn std::error:Error> in a way that supports downcasting (at the cost of backtraces), via a new vtable method. The unsafe blocks in the new code appear to match how boxing and downcasting logic is done in other existing vtable methods.

1.0.79 — diff review from 1.0.77 only (older version) safe-to-deploy

From zcash/rust-ecosystem copy of zcash/zcash. By Jack Grigg.

Build script changes are to refactor the existing probe into a separate file (which removes a filesystem write), and adjust how it gets rerun in response to changes in the build environment.

1.0.66 — diff review from 1.0.62 only (older version) safe-to-deploy

From bytecodealliance/wasmtime. By Alex Crichton.

This update looks to be related to minor fixes and mostly integrating with a nightly feature in the standard library for backtrace integration. No undue unsafe is added and nothing unsurprising for the anyhow crate is happening here.

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.

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

The current version of Anyhow is 1.0.101.

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

by weiznich on 2024-02-29

Review 1.0.75 to 1.0.80 Mostly refactorings related to backtraces and supporting them in newer rust versions

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 anyhow. Alternatively, you can download the tarball of anyhow v1.0.101 or view the source online.