0.8.0 (current)
From bytecodealliance/wasmtime. By Alex Crichton.
These reviews are from cargo-vet. To add your review, set up cargo-vet and submit your URL to its registry.
0.8.0 (current)
From google/supply-chain copy of chromium. By Lukasz Anforowicz.
This delta audit has been reviewed in https://crrev.com/c/5811890
The delta can be inspected at https://diff.rs/miniz_oxide/0.7.4/0.8.0
and is fairly small (changes related to const fn and to adler2
switch).
I've grepped for -i cipher, -i crypto, \bfs\b, \bnet\b, and
\bunsafe\b. There were no hits (except for comments in core.rs
and in Readme.md).
The current version of miniz_oxide is 0.8.0.
0.7.2 — diff review from 0.7.1 only (older version)
From zcash/rust-ecosystem copy of zcash/zcash. Audited without comment by Daira Emma Hopwood.
0.7.1 — diff review from 0.6.2 only (older version)
From google/supply-chain copy of chromium. Audited without comment by George Burgess IV.
0.7.1 (older version)
From kornelski/crev-proofs copy of git.savannah.gnu.org.
Packaged for Guix (crates-io)
0.6.2 — diff review from 0.5.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.
- 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-0 (implies ub-risk-1)
-
No unsafe code.
Full description of the audit criteria can be found at https://github.com/google/rust-crate-audits/blob/main/auditing_standards.md#ub-risk-0
- ub-risk-1 (implies ub-risk-2)
Implied by other criteria
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
- ub-risk-2 (implies ub-risk-3)
Implied by other criteria
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
These reviews are from Crev, a distributed system for code reviews. To add your review, set up cargo-crev.
The current version of miniz_oxide is 0.8.0.
0.4.2 (older version) Thoroughness: Low Understanding: Low
Approved without comment by kornelski on 2020-09-14
0.3.7 (older version) Thoroughness: None Understanding: Low
by inflation on 2021-11-08
Used by png
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 miniz_oxide. Alternatively, you can download the tarball of miniz_oxide v0.8.0 or view the source online.
Minor updates, using new Rust features like
const, no major changes.