retry
v2.2.0 GrowingUtilities for retrying operations that can fail.
Quick Verdict
- โStable API (2.x for 11+ years)
- โMassive adoption (1.3K crates depend on it)
- โTiny footprint (8KB, 1 deps)
- โPermissive license (MIT)
Security
Deep Insights
2.1M downloads in the last 30 days (69.2K/day), up 22% from the previous period.
1.3K crates depend on retry. Strong ecosystem adoption means battle-tested code and long-term stability.
The API has been stable (1.x) for over 11 years with 15 releases. This level of maturity means you can depend on it without worrying about breaking changes.
Only 1 direct dependencies. Lean dependency tree means faster builds and lower supply chain risk.
At 8KB, retry is lightweight. Small crate size correlates with focused, well-scoped functionality.
Notable dependents include testcontainers-modules, openidconnect, syd, dogstatsd, systemd-journal-logger. When high-quality crates choose retry, 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
Version Adoption
Release Timeline
Feature Flags
default =["random"]