tracing
Cargov0.1.44Application-level tracing for Rust.
Not recommended for new projects
No — tracing should not be adopted for new projects. No license declared — you have no explicit right to use this code.
- ?Adoption: grade ?, Not reported by this registry.
No download data reported for this package yet.
- BMaintenance: grade B, Good.
Last published 265 days ago. 4 releases in the last 2 years.
- AWeight: grade A, Excellent.
Zero runtime dependencies.
- ASupply chain: grade A, Excellent.
No install scripts, 2 maintainers, and a contained dependency surface.
- FLicense: grade F, Failing.
No license declared — you have no explicit right to use this code.
Grades are computed deterministically from registry metadata collected by PackageGraph — downloads, dependents, publish dates, the resolved dependency tree, maintainer count, and declared licenses. No third-party scores are used.
Install cost
What you actually take on by adding tracing to a project.
Runtime packages this one declares itself.
Distinct packages in the full runtime tree, deduplicated the way a package manager would.
Unpacked size of this package plus its entire runtime tree.
Longest resolved dependency chain below this package.
Compatibility
- Rust edition
- No constraint declared
tracing vs the alternatives
Packages solving a similar problem in the cargo ecosystem, compared on the signals that drive an adoption decision.
| Package | Weekly downloads | Dependents | License | Last release |
|---|---|---|---|---|
| tracingthis page | 0 | 0 | — | 8 months ago |
| tokio | 0 | 0 | — | 1 day ago |
| async-trait | 0 | 0 | — | 1 day ago |
| log | 0 | 0 | — | 1 day ago |
| actix-web | 0 | 0 | — | 1 day ago |
Release history
3 releases in the last two years, typically about 51 days apart.
| Version | Published | Size | License |
|---|---|---|---|
| 0.1.44latest | 8 months ago | — | MIT |
| 0.1.43 | 9 months ago | — | MIT |
| 0.1.42 | 9 months ago | — | MIT |
| 0.1.41 | 1 year ago | — | MIT |
| 0.1.40 | 2 years ago | — | MIT |
| 0.1.39 | 2 years ago | — | MIT |
| 0.1.38 | 3 years ago | — | MIT |
| 0.1.37 | 3 years ago | — | MIT |
| 0.1.36 | 4 years ago | — | MIT |
| 0.1.35 | 4 years ago | — | MIT |
| 0.1.34 | 4 years ago | — | MIT |
| 0.1.33 | 4 years ago | — | MIT |
| 0.1.32 | 4 years ago | — | MIT |
| 0.1.31 | 4 years ago | — | MIT |
| 0.1.30 | 4 years ago | — | MIT |
Overview
tracing is an Cargo package that application-level tracing for Rust. The latest version is 0.1.44.
Who should use it
Teams working in the Cargo ecosystem who need application-level tracing for Rust and value a focused solution.
When not to use it
Consider an alternative if you need to or if a more actively-maintained option better fits your Cargo stack.
Pros
- Zero runtime dependencies — minimal footprint.
Cons
- No license detected — review usage terms before adopting.
Auto-generated from collected registry metadata. No external claims are inferred.
Maintainers
Frequently asked questions
Should I use tracing?
No — tracing should not be adopted for new projects. No license declared — you have no explicit right to use this code.
How do I install tracing?
Run `cargo add tracing` to add tracing to your Cargo project.
What license is tracing released under?
No license was detected in tracing's metadata; review the repository before use.
Is tracing still maintained?
The most recent release of tracing (v0.1.44) was published 8 months ago.