0.1.10 (current)
From mozilla/supply-chain copy of hg. Audited without comment by Mike Hommey.
These reviews are from cargo-vet. To add your review, set up cargo-vet and submit your URL to its registry.
0.1.10 (current)
From kornelski/crev-proofs copy of git.savannah.gnu.org.
The current version of matches is 0.1.10.
0.1.9 (older version)
From mozilla/supply-chain copy of hg. By Bobby Holley.
This is a trivial crate.
0.1.8 (older version)
From kornelski/crev-proofs copy of salsa.debian.org.
Packaged for Debian (stable). Changelog:
- Package matches 0.1.8 from crates.io using debcargo 2.2.6
- Fix description-too-long
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 matches is 0.1.10.
0.1.9 (older version) Thoroughness: Low Understanding: High
by gitlab.com/KonradBorowski on 2021-09-26
Does exactly what it's supposed to. For new projects it may make sense to
use matches! macro from standard library (https://doc.rust-lang.org/std/macro.matches.html),
but it's fine to use dependencies that use matches crate.
0.1.8 (older version) Thoroughness: High Understanding: High
by niklasf on 2021-02-08
Straight forward utilities. The matches! macro is now part of the standard library.
0.1.8 (older version) Thoroughness: Medium Understanding: Medium
Approved without comment by johnlepikhin on 2020-11-14
0.1.8 (older version) Thoroughness: Low Understanding: Medium
by GTRI-nathan on 2020-10-13
Tiny crate, does what it says in a clear way.
0.1.8 (older version) Thoroughness: Low Understanding: Medium
by IslandUsurper on 2019-08-29
Ran cargo test which passed. Seeing nested calls to matches! in the tests
was unexpected, but look like they would be hard to abuse or mis-use.
0.1.8 (older version) Thoroughness: Medium Understanding: Medium
by MaulingMonkey on 2019-07-23
Trivial, looks correct, looks tested. cfg!(debug_assertions) is a sane cfg.
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 matches. Alternatively, you can download the tarball of matches v0.1.10 or view the source online.
Packaged for Guix (crates-io)