1.0.2 (older version)
From kornelski/crev-proofs copy of salsa.debian.org.
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 Mio is 1.0.3.
1.0.2 (older version)
From kornelski/crev-proofs copy of salsa.debian.org.
1.0.1 — diff review from 0.8.8 only (older version)
From mozilla/supply-chain copy of hg. Audited without comment by Mike Hommey.
0.8.11 — diff review from 0.8.10 only (older version)
From zcash/rust-ecosystem copy of zcash/zcash. Audited without comment by Daira Emma Hopwood.
0.8.10 (older version)
From kornelski/crev-proofs copy of git.savannah.gnu.org.
Packaged for Guix (crates-io)
0.8.9 — diff review from 0.8.5 only (older version)
From google/supply-chain copy of fuchsia. By David Koloski.
Audited at https://fxrev.dev/946305
0.8.8 (older version)
From google/supply-chain copy of chromium. Audited without comment by Vovo Yang.
0.8.8 — diff review from 0.8.6 only (older version)
From zcash/rust-ecosystem copy of zcash/zcash. Audited without comment by str4d.
0.8.8 — diff review from 0.8.6 only (older version)
From bytecodealliance/wasmtime. By Alex Crichton.
Mostly OS portability updates along with some minor bugfixes.
0.8.6 — diff review from 0.8.5 only (older version)
From zcash/rust-ecosystem copy of zcash/zcash. By Jack Grigg.
New unsafe
usages:
NonZeroU8::new_unchecked
: I verified the constant is non-zero.syscall!(close(socket))
calls before returning errors.0.7.14 (older version)
From google/supply-chain copy of chromium. Audited without comment by ChromeOS.
0.7.7 (older version)
From google/supply-chain copy of chromium. Audited without comment by Android Legacy.
0.6.23 — diff review from 0.6.21 only (older version)
From mozilla/supply-chain copy of hg. Audited without comment by Bobby Holley.
cargo-vet does not verify reviewers' identity. You have to fully trust the source the audits are from.
This crate can be compiled, run, and tested on a local workstation or in controlled automation without surprising consequences. More…
This crate will not introduce a serious security vulnerability to production software exposed to untrusted input. More…
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.
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.
Negligible unsoundness or average soundness.
Full description of the audit criteria can be found at https://github.com/google/rust-crate-audits/blob/main/auditing_standards.md#ub-risk-2
Mild unsoundness or suboptimal soundness.
Full description of the audit criteria can be found at https://github.com/google/rust-crate-audits/blob/main/auditing_standards.md#ub-risk-3
Extreme unsoundness.
Full description of the audit criteria can be found at https://github.com/google/rust-crate-audits/blob/main/auditing_standards.md#ub-risk-4
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 Mio is 1.0.3.
0.6.16 (older version) Thoroughness: None Understanding: None
by oherrala on 2019-04-28
There's a known memory leak when used in Windows since at least 2017. This can lead to denial of service if affected process is killed due to memory consumption or degration of performance if operating system runs out of memory. Upstream issues: https://github.com/tokio-rs/mio/issues/776 https://github.com/tokio-rs/mio/issues/919
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 mio
. Alternatively, you can download the tarball of mio v1.0.3 or view the source online.
Only in debcargo (unstable). Changelog: