1.4.0 — diff review from 1.2.0 only (current)
From zcash/rust-ecosystem copy of zcash/zcash. By str4d.
These reviews are from cargo-vet. To add your review, set up cargo-vet and submit your URL to its registry.
1.4.0 (current)
From kornelski/crev-proofs copy of git.savannah.gnu.org.
Packaged for Guix (crates-io)
The current version of Proptest is 1.4.0.
1.0.0 (older version)
From kornelski/crev-proofs copy of salsa.debian.org.
Only in debcargo (unstable). Changelog:
- Team upload.
- Package proptest 1.0.0 from crates.io using debcargo 2.6.0
- When bumping regex-syntax version also bump regex version correspondingly.
- Bump regex-syntax to 0.8 and regex to 1.10
0.10.1 (older version)
From google/supply-chain copy of google/rust-crate-audits. By Manish Goregaokar.
Reviewed in CL 615011355 Not safe with hardware_rng feature on platforms without RDRAND support. Should bubble up the invariant or have a feature test assertion
cargo-vet does not verify reviewers' identity. You have to fully trust the source the audits are from.
- ub-risk-3 (implies ub-risk-4)
-
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
- 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
Implied by other criteria
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
This review is from Crev, a distributed system for code reviews. To add your review, set up cargo-crev.
The current version of Proptest is 1.4.0.
0.8.7 (older version) Thoroughness: None Understanding: Medium
by cyplo on 2019-05-02
Skimmend through sources, looking for code smells, looks okay, some functions could be shorter to improve readability.
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 proptest. Alternatively, you can download the tarball of proptest v1.4.0 or view the source online.
Adds support for generating arbitrary
PathBufs, but as this crate is intended for fuzzing in test environments this is within its expected scope (and the new API would be used intentionally by downstream tests).