Code reviews of the Backtrace crate // Lib.rs

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 Backtrace is 0.3.74.

0.3.71 — diff review from 0.3.69 only (older version) safe-to-deploy

From zcash/rust-ecosystem copy of zcash/zcash. By Daira Emma Hopwood.

This crate inherently requires a lot of unsafe code, but the changes look plausible.

0.3.69 — diff review from 0.3.68 only (older version) safe-to-run, does-not-implement-crypto

From google/supply-chain copy of chromium. Audited without comment by George Burgess IV.

0.3.69 — diff review from 0.3.67 only (older version) safe-to-deploy

From zcash/rust-ecosystem copy of zcash/zcash. By str4d.

Changes to unsafe blocks:

New call to GetCurrentProcessId on Windows, to help generate a process-unique name to use inside an existing CreateMutexA call.
Uses libc::mmap64 on Linux instead of libc::mmap.
Alters Stash to allow caching more than one Mmap; the existing unsafe safety condition continues to be applicable.

There are also several more places where DWARF data is mmapped from a filesystem path and then loaded. These appear to all derive from existing paths that themselves were already being mmapped and loaded.

0.3.69 (older version) unknown

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

Only in debcargo (unstable). Changelog:

Team upload.
Package backtrace 0.3.69 from crates.io using debcargo 2.6.1
Upload to unstable (Closes: #1055090)

0.3.69 (older version) unknown

From kornelski/crev-proofs copy of git.savannah.gnu.org.

Packaged for Guix (crates-io)

0.3.67 — diff review from 0.3.66 only (older version) safe-to-run

From bytecodealliance/wasmtime. By Alex Crichton.

This change introduced a new means of learning the current exe by parsing Linux-specific constructs and does not constitute any major changes to the crate.

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…

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.

safe-to-deploy (implies safe-to-run)

This crate will not introduce a serious security vulnerability to production software exposed to untrusted input. More…

unknown

May have been packaged automatically without a review

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 backtrace. Alternatively, you can download the tarball of backtrace v0.3.74 or view the source online.