tracing-error
v0.2.1 GrowingUtilities for enriching errors with `tracing`.
Quick Verdict
- ✕Not updated for 1+ year
- !Pre-1.0: API may have breaking changes
- ✓Massive adoption (3.4K crates depend on it)
- ✓Team maintained (2 owners)
- ✓Tiny footprint (14KB, 2 deps)
Security
Deep Insights
3.3M downloads in the last 30 days (111.2K/day), up 36% from the previous period.
3.4K crates depend on tracing-error. Strong ecosystem adoption means battle-tested code and long-term stability.
The primary maintainer publishes 53 crates. This suggests deep Rust expertise and long-term commitment to the ecosystem.
Despite being 6+ years old, tracing-error hasn't reached 1.0 yet. Expect potential API changes between versions.
Only 2 direct dependencies. Lean dependency tree means faster builds and lower supply chain risk.
At 14KB, tracing-error is lightweight. Small crate size correlates with focused, well-scoped functionality.
Notable dependents include tracing-opentelemetry, color-eyre, color-spantrace, bevy_log, error-stack. When high-quality crates choose tracing-error, it's a strong quality signal.
Health Breakdown
Recency, release consistency, active ratio
Yanked ratio, deps, size, maturity, features
Reverse deps, ownership, ecosystem
Downloads, momentum, growth trend
Docs, repo, license, metadata
Download Trend
Top Dependents
Most downloaded crates that depend on tracing-error
Version Adoption
Release Timeline
Feature Flags
default =["traced-error"]
