Crates / num_enum_derive / Maintained?
Rust crate maintenance · data Oct 24, 2026
Is num_enum_derive still maintained?
Short answerYes, on a slow release cadence. num_enum_derive's newest version, 0.7.6, shipped on Mar 15, 2026 (7 months ago). It has had 1 release in the last 12 months and 3 in 24, and 25 non-yanked versions since 2019. 2 crates depend on it and it gets 760,485 real downloads a day.
The signals
- Last release: 7 months ago (0.7.6, Mar 15, 2026).
- Release rhythm: 1 in the last year, 3 in two.
- Still used: 760,485 real downloads a day, quiet-day trend -3% against the field.
- Pre-1.0: 0.7.6; minor bumps may break you, so pin the minor version.
- Yanked versions: 1 (a normal sign of a maintainer fixing a bad release).
Releases per quarter, last 2 years
| Quarter | Releases | |
|---|---|---|
| Oct 27 to Jan 25, 2025 | 0 | |
| Jan 26 to Apr 26, 2025 | 0 | |
| Apr 27 to Jul 26, 2025 | 1 | |
| Jul 27 to Oct 25, 2025 | 1 | |
| Oct 26 to Jan 24, 2026 | 0 | |
| Jan 25 to Apr 25, 2026 | 1 | |
| Apr 26 to Jul 25, 2026 | 0 | |
| Jul 26 to Oct 24, 2026 | 0 |
Rules
From crates.io release history (non-yanked versions), fetched Oct 24, 2026: last release within 6 months = actively maintained; within 18 months = slow cadence; older with 1,000+ dependents = quiet and widely relied on; otherwise quiet. We do not read commits or issues: a crate can be finished and safe without new releases, and active on GitHub without publishing. Before you rely on it, look at the repository for recent commits and open issues. Run cargo audit for security advisories.
Up next
The full numbers: Few direct dependents and steady. Chart, alternatives and badge.num_enum_deriveRust crate. Internal implementation details for ::num_enum (Procedural macros to make inter-operation between primitives and enums easier). Real use: 760K downloads a...Read it next →Also worth your time