Code reviews of the codespan-reporting crate // Lib.rs

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

0.12.0 — diff review from 0.11.1 only (current) safe-to-deploy

From mozilla/supply-chain copy of hg. Audited without comment by Erich Gubler.

The current version of codespan-reporting is 0.12.0.

0.11.1 (older version) safe-to-deploy

From bytecodealliance/wasmtime. By Jamey Sharp.

This library uses forbid(unsafe_code) and has no filesystem or network I/O.

0.11.1 (older version) safe-to-run, does-not-implement-crypto

From google/supply-chain copy of chromium. By Dana Jansens.

Reviewed in https://crrev.com/c/5171063

Previously reviewed during security review and the audit is grandparented in.

0.11.1 (older version) safe-to-run

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

Packaged for Debian (stable). Changelog:

Team upload.
Package codespan-reporting 0.11.1 from crates.io using debcargo 2.6.0
Stop pointlessly patching version of insta dev-dependency.
Disable "peg_calculator" example as it needs rustyline and peg.

[ Matthias Geiger ]

Patched out dev-dependencies on rustyline and peg.
Package codespan-reporting 0.11.1 from crates.io using debcargo 2.6.0

0.11.1 (older version) unknown

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.

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…

does-not-implement-crypto (implies crypto-safe)

Inspection reveals that the crate in question does not attempt to implement any cryptographic algorithms on its own.

Note that certification of this does not require an expert on all forms of cryptography: it's expected for crates we import to be "good enough" citizens, so they'll at least be forthcoming if they try to implement something cryptographic. When in doubt, please ask an expert.

crypto-safe

Implied by other criteria

All crypto algorithms in this crate have been reviewed by a relevant expert.

Note: If a crate does not implement crypto, use does-not-implement-crypto, which implies crypto-safe, but does not require expert review in order to audit for.

unknown

May have been packaged automatically without a review

Crates in the crates.io registry are tarball snapshots uploaded by crates' publishers. The registry is not using crates' git repositories. There is absolutely no guarantee that the repository URL declared by the crate belongs to the crate, or that the code in the repository is the code inside the published tarball.

To review the actual code of the crate, it's best to use cargo crev open codespan-reporting. Alternatively, you can download the tarball of codespan-reporting v0.12.0 or view the source online.