Code reviews of the displaydoc crate // Lib.rs

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

0.2.5 (current) Rating: Positive Thoroughness: None Understanding: Low

by kpreid on 2024-06-21

Skimmed; looks fine and contains no surprises for a proc-macro crate.

The current version of displaydoc is 0.2.5.

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

by kornelski on 2020-05-04

Clever

These reviews are from cargo-vet. To add your review, set up cargo-vet and submit your URL to its registry.

0.2.5 (current) unknown

From kornelski/crev-proofs copy of salsa.debian.org.

Only in debcargo (unstable). Changelog:

Package displaydoc 0.2.5 from crates.io using debcargo 2.6.1

The current version of displaydoc is 0.2.5.

0.2.4 (older version) safe-to-deploy

From mozilla/supply-chain copy of hg. Audited without comment by Mike Hommey.

0.2.4 (older version) unknown

From kornelski/crev-proofs copy of git.savannah.gnu.org.

Packaged for Guix (crates-io)

0.2.3 (older version) safe-to-deploy

From mozilla/supply-chain copy of hg. By Makoto Kato.

This crate is convenient macros to implement core::fmt::Display trait. Although unsafe is used for test code to call libc::abort(), it has no unsafe code in this crate. And there is no file access. It meets the criteria for safe-to-deploy.

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

Lib.rs has been able to verify that all files in the crate's tarball, except Cargo.lock, 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 displaydoc. Alternatively, you can download the tarball of displaydoc v0.2.5 or view the source online.