tracing-unwrap
v1.0.1 GrowingExtension traits for logging failed unwraps to a tracing subscriber.
Quick Verdict
- ✕Not updated for 2+ years
- ✓Stable API (1.x for 5+ years)
- ✓Trusted by 104 crates
- ✓Tiny footprint (8KB, 2 deps)
- ✓Permissive license (Apache-2.0/MIT)
Security
Deep Insights
19.0K downloads in the last 30 days (633/day), up 88% from the previous period.
104 crates depend on tracing-unwrap. Reasonable ecosystem adoption, though not yet a core dependency.
The API has been stable (1.x) for over 5 years with 7 releases. This level of maturity means you can depend on it without worrying about breaking changes.
Only 2 direct dependencies. Lean dependency tree means faster builds and lower supply chain risk.
At 8KB, tracing-unwrap is lightweight. Small crate size correlates with focused, well-scoped functionality.
14% of releases have been yanked. Check version history before pinning.
Notable dependents include microformats, resp-result, handlr-regex, microformats-types, reverie-engine. When high-quality crates choose tracing-unwrap, 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-unwrap
Version Adoption
Release Timeline
Feature Flags
default =["panic-quiet"]
