custom_error
v1.9.2 GrowingDefine custom errors without boilerplate using the custom_error! macro.
Quick Verdict
- ✕Not updated for 4+ years
- ✓Stable API (1.x for 7+ years)
- ✓Massive adoption (1.0K crates depend on it)
- ✓Tiny footprint (11KB, 0 deps)
Security
Deep Insights
17.7K downloads in the last 30 days (590/day), up 18% from the previous period.
1.0K crates depend on custom_error. Strong ecosystem adoption means battle-tested code and long-term stability.
custom_error has only 1 owner despite 1.0K dependents. This is a bus-factor concern — consider the implications for long-term support.
The API has been stable (1.x) for over 7 years with 17 releases. This level of maturity means you can depend on it without worrying about breaking changes.
custom_error has no external dependencies — minimal supply chain risk and fast compile times.
At 11KB, custom_error is lightweight. Small crate size correlates with focused, well-scoped functionality.
Notable dependents include broot, zitadel, rrss2imap, aim, timeflake-rs. When high-quality crates choose custom_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 custom_error
Version Adoption
Release Timeline
Feature Flags
default =["std"]
