1.1.0 (current) Thoroughness: Low Understanding: Medium
by derekdreery on 2022-06-21
This review is from Crev, a distributed system for code reviews. To add your review, set up cargo-crev
.
1.1.0 (current) Thoroughness: Low Understanding: Medium
by derekdreery on 2022-06-21
This review is from cargo-vet. To add your review, set up cargo-vet
and submit your URL to its registry.
1.1.0 (current)
From kornelski/crev-proofs copy of git.savannah.gnu.org.
Packaged for Guix (crates-io)
cargo-vet does not verify reviewers' identity. You have to fully trust the source the audits are from.
May have been packaged automatically without a review
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 serde_regex
. Alternatively, you can download the tarball of serde_regex v1.1.0 or view the source online.
I took a look at this crate because it seems to be a low-use crate. I checked the code (Cargo.toml and lib/src.rs), it looked sensible and there weren't any red flags (no system calls, build.rs etc). One comment I would make is that the Cargo.toml could do with an
include
field so that the CI config files aren't uploaded with the crate. Minor point though and doesn't affect the safety of the crate.