Lib.rs

› futures-util › Reviews

These reviews are from cargo-vet. To add your review, set up cargo-vet and submit your URL to its registry.

0.3.30 — diff review from 0.3.29 only (current) safe-to-deploy

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

  • Removes build.rs now that it can rely on the target_has_atomic attribute.
  • Almost all changes to unsafe blocks are to either move them around, or replace them with safe method calls.
  • One new unsafe block is added for a slice lifetime transmutation. The slice reconstruction is obviously correct. AFAICT the lifetime transmutation is also correct; the slice's lifetime logically comes from the AsyncBufRead reader inside FillBuf, rather than the Context.

The current version of futures-util is 0.3.30.

0.3.28 (older version) safe-to-run, does-not-implement-crypto

From google/supply-chain copy of chromium. By George Burgess IV.

There's a custom xorshift-based random::shuffle implementation in src/async_await/random.rs. This is doc(hidden) and seems to exist just so that futures-macro::select can be unbiased. Sicne xorshift is explicitly not intended to be a cryptographically secure algorithm, it is not considered crypto.

0.3.26 — diff review from 0.3.25 only (older version) safe-to-deploy

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

Changes to unsafe usage are to split Either::project into Either::as_pin_ref and Either::as_pin_mut. The new code follows the old code's pattern, and also now has SAFETY documentation.

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