Lib.rs

› cpufeatures › Reviews

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) safe-to-deploy

From zcash/rust-ecosystem copy of zcash/zcash. By str4d.

New unsafe block is to call sysctlbyname to detect DIT on Apple ARM64, which is done in the same way as existing target feature checks on that arch.

0.2.11 (older version) unknown

From kornelski/crev-proofs copy of salsa.debian.org.

Only in debcargo (unstable). Changelog:

  • Team upload.
  • Package cpufeatures 0.2.11 from crates.io using debcargo 2.6.1 (Closes: #1056267)
  • Update dont-fail-build-on-unsupported-architectures.patch for new upstream.

0.2.7 — diff review from 0.2.2 only (older version) safe-to-deploy

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.

cargo-vet does not verify reviewers' identity. You have to fully trust the source the audits are from.

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 implies crypto-safe, but does not require expert review in order to audit for.

safe-to-deploy (implies safe-to-run)

This crate will not introduce a serious security vulnerability to production software exposed to untrusted input. More…

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 cpufeatures is 0.2.16.

0.2.12 (older version) Rating: Positive Thoroughness: Low Understanding: Medium

by weiznich on 2024-02-29

Review update from 0.2.11 to 0.2.12

  • Added some more instructions

0.1.5 (older version) Rating: Positive 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.