Rust advisories / fake_clock
UnmaintainedRUSTSEC-2020-0065 · fake_clock
RUSTSEC-2020-0065: crate has been renamed to `sn_fake_clock`
Short answerNot a bug report: fake_clock is no longer maintained, so future security issues will not be fixed. Plan to move to a maintained alternative.
| Crate | fake_clock |
|---|---|
| Type | Unmaintained |
| Affected versions | Every version. |
| Fixed in | not applicable (the crate is unmaintained) |
| Severity | not scored |
| Published | 2020-11-02 |
| Last changed | 2020-11-02 |
| 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-2020-0065"toignorein.cargo/audit.tomlordeny.toml, with a comment saying why. - Find who pulls it in:
cargo tree -i fake_clock.
Details from the advisory
This crate has been renamed from fake_clock to sn_fake_clock.
The new repository location is:
<https://github.com/maidsafe/sn_fake_clock>
References
- Package: crates.io/crates/fake_clock
- Advisory: rustsec.org/advisories/RUSTSEC-2020-0065.html
- Web: github.com/maidsafe/sn_fake_clock/pull/38
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?