Crates / base64ct / Maintained?
Rust crate maintenance · data Oct 24, 2026
Is base64ct still maintained?
Short answerYes, on a slow release cadence. base64ct's newest version, 1.8.3, shipped on Jan 12, 2026 (9 months ago). It has had 3 releases in the last 12 months and 7 in 24, and 19 non-yanked versions since 2021. 439 crates depend on it and it gets 1,305,115 real downloads a day.
The signals
- Last release: 9 months ago (1.8.3, Jan 12, 2026).
- Release rhythm: 3 in the last year, 7 in two.
- Still used: 1,305,115 real downloads a day, quiet-day trend +2% against the field.
- Yanked versions: 12 (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 | 3 | |
| Apr 27 to Jul 26, 2025 | 1 | |
| Jul 27 to Oct 25, 2025 | 0 | |
| Oct 26 to Jan 24, 2026 | 3 | |
| Jan 25 to Apr 25, 2026 | 0 | |
| Apr 26 to Jul 25, 2026 | 0 | |
| Jul 26 to Oct 24, 2026 | 0 |
If you need something more active
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: Established and steady. Chart, alternatives and badge.base64ctRust crate. Pure Rust implementation of Base64 (RFC 4648) which avoids any usages of data-dependent branches/LUTs and thereby provides portable "best effort"...Read it next →Also worth your time