0.1.40 (current)
From kornelski/crev-proofs copy of salsa.debian.org.
These reviews are from cargo-vet. To add your review, set up cargo-vet and submit your URL to its registry.
0.1.40 (current)
From kornelski/crev-proofs copy of git.savannah.gnu.org.
Packaged for Guix (crates-io)
The current version of Tracing is 0.1.40.
0.1.39 (older version)
From google/supply-chain copy of google/rust-crate-audits. By Taylor Cramer.
Reviewed in CL 573852894 Issues found:
0.1.37 — diff review from 0.1.34 only (older version)
From bytecodealliance/wasmtime. By Alex Crichton.
A routine set of updates for the tracing crate this includes minor refactorings, addition of benchmarks, some test updates, but overall nothing out of the ordinary.
0.1.37 — diff review from 0.1.36 only (older version)
From mozilla/supply-chain copy of hg. Audited without comment by Mike Hommey.
0.1.35 (older version)
From google/supply-chain copy of chromium. Audited without comment by ChromeOS.
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…
- ub-risk-4
-
Extreme unsoundness.
Full description of the audit criteria can be found at https://github.com/google/rust-crate-audits/blob/main/auditing_standards.md#ub-risk-4
- unknown
-
May have been packaged automatically without a review
This review is from Crev, a distributed system for code reviews. To add your review, set up cargo-crev.
The current version of Tracing is 0.1.40.
0.1.22 (older version) Thoroughness: Low Understanding: Low
Approved without comment by kornelski on 2020-12-15
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 tracing. Alternatively, you can download the tarball of tracing v0.1.40 or view the source online.
Only in debcargo (unstable). Changelog: