1.39.3 (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 Tokio is 1.41.1.
1.37.0 — diff review from 1.35.1 only (older version)
From zcash/rust-ecosystem copy of zcash/zcash. By Daira Emma Hopwood.
Cursory review, but new and changed uses of unsafe code look fine, as far as I can see.
1.36.0 (older version)
From kornelski/crev-proofs copy of git.savannah.gnu.org.
Packaged for Guix (crates-io)
1.35.1 — diff review from 1.35.0 only (older version)
From zcash/rust-ecosystem copy of zcash/zcash. Audited without comment by str4d.
1.29.1 (older version)
From google/supply-chain copy of chromium. Audited without comment by Vovo Yang.
1.25.2 — diff review from 1.20.5 only (older version)
From google/supply-chain copy of fuchsia. By David Koloski.
Reviewed at https://fxrev.dev/906324
1.18.4 — diff review from 1.18.1 only (older version)
From bytecodealliance/wasmtime. By Alex Crichton.
This looks to be a minor release primarily to fix a security-related Windows issue plus some reorganization around lazy initialization. Altogether nothing amiss here.
1.2.0 (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-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.- ub-risk-2 (implies ub-risk-3)
-
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
- ub-risk-3 (implies ub-risk-4)
Implied by other criteria
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
- ub-risk-4
Implied by other criteria
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
- 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 tokio. Alternatively, you can download the tarball of tokio v1.41.1 or view the source online.
Only in debcargo (unstable). Changelog: