0.13.0 (current)
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.
0.13.0 (current)
From kornelski/crev-proofs copy of salsa.debian.org.
The current version of Itertools is 0.13.0.
0.12.1 — diff review from 0.10.5 only (older version)
From bytecodealliance/wasmtime. By Nick Fitzgerald.
Minimal unsafe
usage. Few blocks that existed looked reasonable. Does what it
says on the tin: lots of iterators.
0.12.1 (older version)
From kornelski/crev-proofs copy of git.savannah.gnu.org.
Packaged for Guix (crates-io)
0.11.0 — diff review from 0.10.5 only (older version)
From google/supply-chain copy of chromium. Audited without comment by Yu-An Wang.
0.11.0 (older version)
From google/supply-chain copy of chromium. By agl.
This is 12K lines of code, plus 6K lines of tests and benchmarks. It has minimal use of unsafe and so I have paged though it all with "::" highlighted and paid attention to which imported functions are being called.
0.11.0 (older version)
From google/supply-chain copy of google/rust-crate-audits. By Benjamin Saunders.
Reviewed in CL 566337310
0.11.0 — diff review from 0.10.5 only (older version)
From divviup/libprio-rs. Audited without comment by David Cook.
0.10.5 (older version)
From google/supply-chain copy of chromium. Audited without comment by ChromeOS.
0.10.5 — diff review from 0.10.3 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.
This crate can be compiled, run, and tested on a local workstation or in controlled automation without surprising consequences. 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.
Excellent 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-1
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
This crate will not introduce a serious security vulnerability to production software exposed to untrusted input. More…
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 Itertools is 0.13.0.
0.10.1 (older version) Thoroughness: Medium Understanding: High
Approved without comment by samueltardieu on 2022-01-06
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 itertools
. Alternatively, you can download the tarball of itertools v0.13.0 or view the source online.
Only in debcargo (unstable). Changelog: