0.3.31 — diff review from 0.3.28 only (current)
From google/supply-chain copy of chromium. Audited without comment by George Burgess IV.
These reviews are from cargo-vet. To add your review, set up cargo-vet and submit your URL to its registry.
0.3.31 (current)
From kornelski/crev-proofs copy of salsa.debian.org.
The current version of futures-core is 0.3.31.
0.3.30 — diff review from 0.3.29 only (older version)
From zcash/rust-ecosystem copy of zcash/zcash. By str4d.
Removes build.rs now that it can rely on the target_has_atomic attribute.
0.3.30 (older version)
From kornelski/crev-proofs copy of git.savannah.gnu.org.
Packaged for Guix (crates-io)
0.3.28 — diff review from 0.3.27 only (older version)
From zcash/rust-ecosystem copy of zcash/zcash. By Daira Emma Hopwood.
Adds an optimization in unsafe code (https://github.com/rust-lang/futures-rs/pull/2723). The new code in AtomicWaker calls self.waker.get() twice assuming the same resulting pointer, but this appears to be correct because the AtomicWaker is in the required locked state.
0.3.28 — diff review from 0.3.27 only (older version)
From mozilla/supply-chain copy of hg. Audited without comment by Mike Hommey.
0.3.27 (older version)
From bytecodealliance/wasmtime. By Pat Hickey.
Unsafe used to implement a concurrency primitive AtomicWaker. Well-commented and not obviously incorrect. Like my other audits of these concurrency primitives inside the futures family, I couldn't certify that it is correct without formal methods, but that is out of scope for this vetting.
0.3.26 — diff review from 0.3.25 only (older version)
From zcash/rust-ecosystem copy of zcash/zcash. By Jack Grigg.
Adds optional dependency on portable-atomic 1 that can be enabled to replace core::sync::atomic.
0.3.14 (older version)
From google/supply-chain copy of chromium. Audited without comment by Android Legacy.
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 impliescrypto-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
These reviews are from Crev, a distributed system for code reviews. To add your review, set up cargo-crev.
The current version of futures-core is 0.3.31.
0.3.30 (older version) Thoroughness: Low Understanding: Medium
by weiznich on 2024-02-29
Review update from 0.3.29 to 0.3.30
- Removed build script
0.3.17 (older version) Thoroughness: Low Understanding: Medium
by leo60228 on 2021-11-18
Most of what this crate does is simple, and it's very thoroughly commented.
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-core. Alternatively, you can download the tarball of futures-core v0.3.31 or view the source online.
Only in debcargo (unstable). Changelog: