Code review of the Visibility crate // Lib.rs

This review is from cargo-vet. To add your review, set up cargo-vet and submit your URL to its registry.

0.1.1 (current) safe-to-deploy, license-reviewed

From zcash/rust-ecosystem copy of zcash/librustzcash. By Kris Nuttycombe.

Crate has no unsafe code, and sets #![forbid(unsafe_code)].
Crate has no powerful imports, and exclusively provides a proc macro that safely malleates a visibility modifier.

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…

license-reviewed

The license of this crate has been reviewed for compatibility with its usage in this repository.

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 visibility. Alternatively, you can download the tarball of visibility v0.1.1 or view the source online.