0.5.12 — diff review from 0.5.11 only (current)
From mozilla/supply-chain copy of mozilla/glean. By Jan-Erik Rediger.
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 crossbeam-channel is 0.5.12.
0.5.11 (older version)
From kornelski/crev-proofs copy of salsa.debian.org.
Only in debcargo (unstable). Changelog:
- Team upload.
- Package crossbeam-channel 0.5.11 from crates.io using debcargo 2.6.1
- Update fix-tests-no-default-features.patch for new upstream.
0.5.11 (older version)
From kornelski/crev-proofs copy of git.savannah.gnu.org.
Packaged for Guix (crates-io)
0.5.10 — diff review from 0.5.9 only (older version)
From zcash/rust-ecosystem copy of zcash/zcash. By str4d.
Changes to unsafe code are to use MaybeUninit::assume_init_drop (which is
now usable with the new MSRV) instead of dropping via casting.
0.5.8 — diff review from 0.5.4 only (older version)
From bytecodealliance/wasmtime. By Alex Crichton.
This diff does what it says on the tin for this version range, notably fixing a
race condition, improving handling of durations, and additionally swapping out a
spin lock with a lock from the standard library. Minor bits of unsafe code
are modified but that's expected given the nature of this crate.
0.5.8 — diff review from 0.5.7 only (older version)
From google/supply-chain copy of chromium. Audited without comment by George Burgess IV.
0.5.6 — diff review from 0.5.4 only (older version)
From mozilla/supply-chain copy of hg. Audited without comment by Mike Hommey.
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
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 crossbeam-channel. Alternatively, you can download the tarball of crossbeam-channel v0.5.12 or view the source online.
Minimal change fixing a memory leak.