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-beta.0.

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-beta.0.

0.6.2 (older version) Rating: Positive 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) Rating: Positive Thoroughness: Low Understanding: Low

Approved without comment by mgeisler on 2021-05-07

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


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 rand_core. Alternatively, you can download the tarball of rand_core v0.9.0-beta.0 or view the source online.