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 UniCase is 2.8.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
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


These reviews are from Crev, a distributed system for code reviews. To add your review, set up cargo-crev.

The current version of UniCase is 2.8.0.

2.4.0 (older version) Rating: Positive Thoroughness: Low Understanding: Low

Approved without comment by kornelski on 2019-07-08

1.4.2 (older version) Rating: Neutral Thoroughness: Low Understanding: High

by gitlab.com/KonradBorowski on 2019-07-31

Unlike unicase 2 it doesn't use case folding, so 'ß' would be considered different to 'SS'


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