Lib.rs

› fastrand › 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 fastrand is 2.0.2.

2.0.1 (older version) unknown

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

Only in debcargo (experimental). Changelog:

  • Package fastrand 2.0.1 from crates.io using debcargo 2.6.0
  • Remove dev-dependency on wyhash and disable bench that depends on it so the rest of the tests can run.
  • Fix tests with --no-default-features

[ Sylvestre Ledru ]

  • Team upload.
  • Package fastrand 2.0.0 from crates.io using debcargo 2.6.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…

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.

rule-of-two-safe-to-deploy (implies safe-to-deploy)

This is a stronger requirement than the built-in safe-to-deploy criteria, motivated by Chromium's rule-of-two related requirements: https://chromium.googlesource.com/chromium/src/+/master/docs/security/rule-of-2.md#unsafe-code-in-safe-languages

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

Auditors are not required to perform a full logic review of the entire crate. Rather, they must review enough to fully reason about the behavior of all unsafe blocks and usage of powerful imports. For any reasonable usage of the crate in real-world software, an attacker must not be able to manipulate the runtime behavior of these sections in an exploitable or surprising way.

Ideally, ambient capabilities (e.g. filesystem access) are hardened against manipulation and consistent with the advertised behavior of the crate. However, some discretion is permitted. In such cases, the nature of the discretion should be recorded in the notes field of the audit record.

Any unsafe code in this crate must, in general, be kept well-contained, and documentation must exist to describe how Rust's invariants are being upheld despite the unsafe block(s). Nontrivial uses of unsafe must be reviewed by an expert in Rust's unsafety guarantees/non-guarantees.

For crates which generate deployed code (e.g. build dependencies or procedural macros), reasonable usage of the crate should output code which meets the above criteria.

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 fastrand is 2.0.2.

1.8.0 (older version) Rating: Positive Thoroughness: High Understanding: High

by Minoru on 2022-07-25

This new version adds trivial methods to get the seed out of an existing generator. I don't see any problem with this feature.

My recommendation stands: use this as a non-cryptographic PRNG if you don't already depend on rand and want to keep your dependencies to the minimum.

1.7.0 (older version) Rating: Positive Thoroughness: High Understanding: High

by Minoru on 2022-01-26

Show review…

Compared to 1.6.0, the Cargo.toml indicates MSRV of 1.34, and there is a new char() method to generate characters. The code looks clean enough, contains to unsafe, and I don't see any flaws in it.

My recommendation stands: use this as a non-cryptographic PRNG if you don't already depend on rand and want to keep your deps to the minimum.

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 fastrand. Alternatively, you can download the tarball of fastrand v2.0.2 or view the source online.