1.2.0 (older version)
From kornelski/crev-proofs copy of git.savannah.gnu.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 hyper is 1.5.0.
1.2.0 (older version)
From kornelski/crev-proofs copy of git.savannah.gnu.org.
1.0.1 — diff review from 1.0.0-rc.3 only (older version)
From bytecodealliance/wasmtime. By Alex Crichton.
Quite a few changes here relative to the last RC but everything is related to refactorings and such. No new fundamental addition of functionality or substantially new unsafe code.
1.0.1 (older version)
From google/supply-chain copy of google/rust-crate-audits. By Manish Goregaokar, Augie Fackler.
Reviewed in CL 588384310 Issues found:
0.14.28 — diff review from 0.14.27 only (older version)
From zcash/rust-ecosystem copy of zcash/zcash. Audited without comment by str4d.
0.14.27 — diff review from 0.14.26 only (older version)
From zcash/rust-ecosystem copy of zcash/zcash. Audited without comment by str4d.
0.14.27 (older version)
From google/supply-chain copy of chromium. Audited without comment by George Burgess IV.
0.14.27 (older version)
From kornelski/crev-proofs copy of salsa.debian.org.
Only in debcargo (unstable). Changelog:
0.14.24 — diff review from 0.14.23 only (older version)
From mozilla/supply-chain copy of hg. Audited without comment by Mike Hommey.
0.14.24 — diff review from 0.14.23 only (older version)
From zcash/rust-ecosystem copy of zcash/zcash. By Jack Grigg.
Fixes a bug where memory was reserved based on an adversary-controllable size, before the corresponding data was received.
0.14.20 (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…
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.
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
These reviews are from Crev, a distributed system for code reviews. To add your review, set up cargo-crev
.
The current version of hyper is 1.5.0.
0.14.28 (older version) Thoroughness: Low Understanding: Medium
by weiznich on 2024-02-29
Review update from 0.14.27 to 0.14.28
0.10.2 (older version) Thoroughness: None Understanding: None
by dpc on 2019-07-02
Issue: Medium (RUSTSEC-2017-0002)
Crates in the crates.io registry are tarball snapshots uploaded by crates' publishers. The registry is not using crates' git repositories. There is absolutely no guarantee that the repository URL declared by the crate belongs to the crate, or that the code in the repository is the code inside the published tarball.
To review the actual code of the crate, it's best to use cargo crev open hyper
. Alternatively, you can download the tarball of hyper v1.5.0 or view the source online.
Packaged for Guix (crates-web)