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 opaque-debug is 0.3.1.

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 opaque-debug is 0.3.1.

0.3.0 (older version) Rating: Positive Thoroughness: Medium Understanding: Medium

Approved without comment by johnlepikhin on 2020-11-14

0.2.3 (older version) Rating: Strong Positive Thoroughness: High Understanding: High

by LovecraftianHorror on 2022-06-11

Intended for cases where you want a debug format that formats a struct as StructName { ... } to prevent leaking internal state, and it seems to do exactly that.

0.2.3 (older version) Rating: Positive Thoroughness: High Understanding: High

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

Doesn't support generic struts

0.2.2 (older version) Rating: Neutral Thoroughness: High Understanding: High

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

Show review…

Doesn't support generic struts and checks for core/std incorrectly sometimes causing compilation errors when used in Edition 2015 code


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