Rust advisories / chrono-english
UnmaintainedRUSTSEC-2024-0395 · chrono-english
RUSTSEC-2024-0395: The maintainer of chrono-english is unresponsive
Short answerNot a bug report: chrono-english is no longer maintained, so future security issues will not be fixed. Plan to move to a maintained alternative.
| Crate | chrono-english |
|---|---|
| Type | Unmaintained |
| Affected versions | Every version. |
| Fixed in | not applicable (the crate is unmaintained) |
| Severity | not scored |
| Published | 2024-06-24 |
| Last changed | 2024-11-10 |
| Also known as | none |
What to do
- Look for a maintained fork or alternative crate.
- If you cannot move yet, acknowledge it in your audit config so CI stays green while you plan: add
"RUSTSEC-2024-0395"toignorein.cargo/audit.tomlordeny.toml, with a comment saying why. - Find who pulls it in:
cargo tree -i chrono-english.
Details from the advisory
All versions will encounter compilation errors with a chrono version >0.4.35, due to backward incompatible API changes.
User conradludgade reworked the original crate and created a fork with the same API surface called interim.
The fork is better structured and passes the same test suite as chrono-english, ensuring backward compatibility.
References
- Package: crates.io/crates/chrono-english
- Advisory: rustsec.org/advisories/RUSTSEC-2024-0395.html
- Report: github.com/stevedonovan/chrono-english/issues/29
From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.
Up next
Are you affected?Check your whole dependency treePaste Cargo.lock: every advisory, for your exact versions.Read it next →Also worth your time
Did this answer your question?