2.1.1 — diff review from 2.1.0 only (older version)
From zcash/rust-ecosystem copy of zcash/zcash. Audited without comment 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 fastrand is 2.3.0.
2.1.1 (older version)
From kornelski/crev-proofs copy of salsa.debian.org.
2.1.0 — diff review from 2.0.1 only (older version)
From mozilla/supply-chain copy of hg. Audited without comment by Mike Hommey.
2.1.0 — diff review from 2.0.2 only (older version)
From zcash/rust-ecosystem copy of zcash/librustzcash. By Daira Emma Hopwood.
As noted in the changelog, this version produces different output for a given seed. The documentation did not mention stability. It is possible that some uses relying on determinism across the update would be broken.
The new constants do appear to match WyRand v4.2 (modulo ordering issues that I have not checked): https://github.com/wangyi-fudan/wyhash/blob/408620b6d12b7d667b3dd6ae39b7929a39e8fa05/wyhash.h#L145 I have no way to check whether these constants are an improvement or not.
2.0.2 (older version)
From google/supply-chain copy of chromium. Audited without comment by Ying Hsu.
2.0.2 — diff review from 2.0.1 only (older version)
From zcash/rust-ecosystem copy of zcash/zcash. Audited without comment by Daira Emma Hopwood.
2.0.1 — diff review from 2.0.0 only (older version)
From bytecodealliance/wasmtime. By Alex Crichton.
This update had a few doc updates but no otherwise-substantial source code updates.
2.0.1 (older version)
From kornelski/crev-proofs copy of git.savannah.gnu.org.
Packaged for Guix (crates-io)
1.9.0 (older version)
From google/supply-chain copy of chromium. By George Burgess IV.
does-not-implement-crypto is certified because this crate explicitly says
that the RNG here is not cryptographically secure.
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 impliescrypto-safe, but does not require expert review in order to audit for.- ub-risk-0 (implies ub-risk-1)
-
No unsafe code.
Full description of the audit criteria can be found at https://github.com/google/rust-crate-audits/blob/main/auditing_standards.md#ub-risk-0
- ub-risk-1 (implies ub-risk-2)
Implied by other criteria
Excellent soundness.
Full description of the audit criteria can be found at https://github.com/google/rust-crate-audits/blob/main/auditing_standards.md#ub-risk-1
- ub-risk-2 (implies ub-risk-3)
Implied by other criteria
Negligible unsoundness or average soundness.
Full description of the audit criteria can be found at https://github.com/google/rust-crate-audits/blob/main/auditing_standards.md#ub-risk-2
- ub-risk-3 (implies ub-risk-4)
Implied by other criteria
Mild unsoundness or suboptimal soundness.
Full description of the audit criteria can be found at https://github.com/google/rust-crate-audits/blob/main/auditing_standards.md#ub-risk-3
- ub-risk-4
Implied by other criteria
Extreme unsoundness.
Full description of the audit criteria can be found at https://github.com/google/rust-crate-audits/blob/main/auditing_standards.md#ub-risk-4
- 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.3.0.
1.8.0 (older version) 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) 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.3.0 or view the source online.
Only in debcargo (unstable). Changelog: