0.2.14 — diff review from 0.2.13 only (older version)
From zcash/rust-ecosystem copy of zcash/zcash. By str4d.
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 cpufeatures is 0.2.16.
0.2.14 — diff review from 0.2.13 only (older version)
From zcash/rust-ecosystem copy of zcash/zcash. By str4d.
0.2.12 — diff review from 0.2.11 only (older version)
From zcash/rust-ecosystem copy of zcash/zcash. Audited without comment by Daira Emma Hopwood.
0.2.11 (older version)
From kornelski/crev-proofs copy of salsa.debian.org.
Only in debcargo (unstable). Changelog:
0.2.11 (older version)
From kornelski/crev-proofs copy of git.savannah.gnu.org.
Packaged for Guix (crates-io)
0.2.9 — diff review from 0.2.8 only (older version)
From google/supply-chain copy of chromium. Audited without comment by George Burgess IV.
0.2.8 — diff review from 0.2.7 only (older version)
From mozilla/supply-chain copy of hg. By Gabriele Svelto.
This release contains a single fix for an issue that affected Firefox
0.2.7 — diff review from 0.2.2 only (older version)
From bytecodealliance/wasmtime. By Alex Crichton.
This is a minor update that looks to add some more detected CPU features and various other minor portability fixes such as MIRI support.
0.2.6 — diff review from 0.2.5 only (older version)
From zcash/rust-ecosystem copy of zcash/zcash. Audited without comment by ebfull.
0.2.5 — diff review from 0.2.4 only (older version)
From mozilla/supply-chain copy of hg. Audited without comment by Mike Hommey.
0.2.5 — diff review from 0.2.2 only (older version)
From zcash/rust-ecosystem copy of zcash/zcash. By Jack Grigg.
Unsafe changes just introduce #[inline(never)]
wrappers.
cargo-vet does not verify reviewers' identity. You have to fully trust the source the audits are from.
This crate will not introduce a serious security vulnerability to production software exposed to untrusted input. More…
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.
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 cpufeatures is 0.2.16.
0.2.12 (older version) Thoroughness: Low Understanding: Medium
by weiznich on 2024-02-29
Review update from 0.2.11 to 0.2.12
0.1.5 (older version) Thoroughness: Low Understanding: Medium
Approved without comment by kornelski on 2021-08-20
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 cpufeatures
. Alternatively, you can download the tarball of cpufeatures v0.2.16 or view the source online.
New
unsafe
block is to callsysctlbyname
to detect DIT on Apple ARM64, which is done in the same way as existing target feature checks on that arch.