1.0.97 — diff review from 1.0.95 only (current)
From google/supply-chain copy of chromium. By Daniel Cheng.
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.97.
1.0.95 — diff review from 1.0.94 only (older version)
From google/supply-chain copy of chromium. Audited without comment by Adrian Taylor.
1.0.94 — diff review from 1.0.93 only (older version)
From google/supply-chain copy of chromium. By Dustin J. Mitchell.
No behavioral changes
1.0.93 — diff review from 1.0.91 only (older version)
From google/supply-chain copy of chromium. By Lukasz Anforowicz.
ensure! macro tweaks to handle
https://github.com/rust-lang/rfcs/blob/master/text/2582-raw-reference-mir-operator.md
1.0.91 — diff review from 1.0.89 only (older version)
From google/supply-chain copy of chromium. By Liza Burakova.
Minimal changes
1.0.86 (older version)
From kornelski/crev-proofs copy of git.savannah.gnu.org.
Packaged for Guix (crates-io)
1.0.86 (older version)
From kornelski/crev-proofs copy of salsa.debian.org.
Only in debcargo (unstable). Changelog:
- Team upload.
- Package anyhow 1.0.86 from crates.io using debcargo 2.6.1
1.0.83 — diff review from 1.0.82 only (older version)
From zcash/rust-ecosystem copy of zcash/librustzcash. Audited without comment by Daira-Emma Hopwood.
1.0.83 — diff review from 1.0.82 only (older version)
From google/supply-chain copy of chromium. By Dana Jansens.
No change to UB-risk profile either.
1.0.82 — diff review from 1.0.79 only (older version)
From zcash/rust-ecosystem copy of zcash/zcash. Audited without comment by Daira-Emma Hopwood.
1.0.79 — diff review from 1.0.77 only (older version)
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.75 — diff review from 1.0.72 only (older version)
From google/supply-chain copy of chromium. Audited without comment by George Burgess IV.
1.0.71 — diff review from 1.0.69 only (older version)
From bytecodealliance/wasmtime. Audited without comment by Pat Hickey.
1.0.70 — diff review from 1.0.69 only (older version)
From zcash/rust-ecosystem copy of zcash/zcash. Audited without comment by ebfull.
1.0.69 — diff review from 1.0.68 only (older version)
From zcash/rust-ecosystem copy of zcash/zcash. Audited without comment by Jack Grigg.
1.0.69 — diff review from 1.0.68 only (older version)
From mozilla/supply-chain copy of hg. Audited without comment by Mike Hommey.
1.0.68 (older version)
From fermyon/spin. By Vaughn Dice.
CI and test updates plus minor Rust efficiency improvements.
1.0.68 (older version)
From google/supply-chain copy of chromium. Audited without comment by ChromeOS.
1.0.66 — diff review from 1.0.62 only (older version)
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.
1.0.66 (older version)
From EmbarkStudios/rust-ecosystem. By Embark.
New unsafe usage, looks sane. Expert maintainer
1.0.65 (older version)
From fermyon/spin. Audited without comment by Radu Matei.
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 impliescrypto-safe, but does not require expert review in order to audit for.- 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 Anyhow is 1.0.97.
1.0.80 (older version) 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
Lib.rs has been able to verify that all files in the crate's tarball, except Cargo.lock,
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 anyhow. Alternatively, you can download the tarball of anyhow v1.0.97 or view the source online.
Only minor changes to comments, tests, and clippy expectations.