0.6.4 (older version)
From google/supply-chain copy of chromium. Audited without comment by Android Legacy.
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 rand_core is 0.9.0-alpha.1.
0.6.4 — diff review from 0.6.3 only (older version)
From mozilla/supply-chain copy of hg. Audited without comment by Mike Hommey.
0.6.4 (older version)
From kornelski/crev-proofs copy of git.savannah.gnu.org.
0.6.3 (older version)
From divviup/libprio-rs. Audited without comment by David Cook.
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…
- 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 rand_core is 0.9.0-alpha.1.
0.6.2 (older version) Thoroughness: Medium Understanding: Medium
by mgeisler on 2021-05-07
The delta to 0.6.1 is safe: two assertions have been tightened.
0.6.1 (older version) Thoroughness: Low Understanding: Low
Approved without comment by mgeisler on 2021-05-07
0.5.1 (older version) Thoroughness: Medium Understanding: Medium
by Cerber-Ursi on 2021-11-27
A de-facto standard crate for random number generation, highly validated by common practice.
Can't really give the "strong" review, since there are several uses of copy_nonoverlapping,
which either deserve a comment with a little explanation or can be safely replaced with
copy_from_slice. Also, noted some suboptimal ergonomic for internal macro, when the size
of type in use is passed explicitly and sometimes unchecked.
However, it does its work well, and to my opinion is a good (just not excellent) example
of what the idiomatic Rust code should be.
0.4.2 (older version) Thoroughness: None Understanding: None
by dpc on 2019-09-05
-
Issue: Medium (github.com/RustSec/advisory-db/pull/149)
https://github.com/RustSec/advisory-db/pull/149, RustSec ID not assigned yet
Lib.rs has been able to verify that all files in the crate's tarball are in the crate's repository. 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 rand_core. Alternatively, you can download the tarball of rand_core v0.9.0-alpha.1 or view the source online.
Packaged for Guix (crates-io)