1.9.0 — diff review from 1.8.0 only (current)
From google/supply-chain copy of chromium. By Dustin J. Mitchell.
These reviews are from cargo-vet. To add your review, set up cargo-vet
and submit your URL to its registry.
1.9.0 — diff review from 1.8.0 only (current)
From google/supply-chain copy of chromium. By Dustin J. Mitchell.
The current version of Bytes is 1.9.0.
1.8.0 — diff review from 1.7.2 only (older version)
From google/supply-chain copy of chromium. By Liza Burakova.
smol change, does not add unsafe code, majority of change is new tests
1.7.2 — diff review from 1.7.1 only (older version)
From google/supply-chain copy of chromium. Audited without comment by Lukasz Anforowicz.
1.7.2 — diff review from 1.7.1 only (older version)
From zcash/rust-ecosystem copy of zcash/zcash. Audited without comment by str4d.
1.7.2 (older version)
From kornelski/crev-proofs copy of salsa.debian.org.
Only in debcargo (unstable). Changelog:
1.6.0 — diff review from 1.5.0 only (older version)
From zcash/rust-ecosystem copy of zcash/zcash. By Daira Emma Hopwood.
There is significant use of unsafe
code, but safety requirements are well documented
and appear correct as far as I can see.
1.5.0 — diff review from 1.4.0 only (older version)
From google/supply-chain copy of chromium. Audited without comment by agl.
1.4.0 (older version)
From google/supply-chain copy of chromium. Audited without comment by George Burgess IV.
1.4.0 — diff review from 1.3.0 only (older version)
From zcash/rust-ecosystem copy of zcash/zcash. By Jack Grigg.
Adds a mem::forget
as part of avoiding Vec::into_boxed_slice
when it would reallocate.
I checked that the required semantics of mem::forget
are maintained, but it seems like
ManuallyDrop
should also work here and be compatible with their MSRV.
1.4.0 — diff review from 1.3.0 only (older version)
From mozilla/supply-chain copy of hg. Audited without comment by Mike Hommey.
1.4.0 (older version)
From kornelski/crev-proofs copy of git.savannah.gnu.org.
Packaged for Guix (crates-io)
1.0.1 (older version)
From google/supply-chain copy of chromium. Audited without comment by Android Legacy.
0.5.6 (older version)
From google/supply-chain copy of chromium. Audited without comment by ChromeOS.
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.
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 Bytes is 1.9.0.
0.4.12 (older version) Thoroughness: Low Understanding: Low
Approved without comment by kornelski on 2019-07-08
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 bytes
. Alternatively, you can download the tarball of bytes v1.9.0 or view the source online.
Reviewed in https://crrev.com/c/6072366.