This project might be open to known security vulnerabilities, which can be prevented by tightening the version range of affected dependencies. Find detailed information at the bottom.

Crate chrono

Dependencies

(10 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 arbitrary^1.0.01.4.2up to date
 defmt^1.0.11.0.1up to date
 iana-time-zone^0.1.450.1.65up to date
 js-sys^0.30.3.88up to date
 num-traits^0.20.2.19up to date
 pure-rust-locales^0.8.20.8.2up to date
 rkyv ⚠️^0.7.430.8.15out of date
 serde^1.0.991.0.228up to date
 wasm-bindgen^0.20.2.111up to date
 windows-link^0.20.2.1up to date

Dev dependencies

(6 total, 1 outdated)

CrateRequiredLatestStatus
 bincode^1.3.03.0.0out of date
 serde_derive^11.0.228up to date
 serde_json^11.0.149up to date
 similar-asserts^1.6.11.7.0up to date
 wasm-bindgen-test^0.30.3.61up to date
 windows-bindgen^0.660.66.0up to date

Security Vulnerabilities

rkyv: Potential Undefined Behaviors in `Arc<T>`/`Rc<T>` impls of `from_value` on OOM

RUSTSEC-2026-0001

The SharedPointer::alloc implementation for sync::Arc<T> and rc::Rc<T> in rkyv/src/impls/alloc/rc/atomic.rs (and rc.rs) does not check if the allocator returns a null pointer on OOM (Out of Memory).

This null pointer can flow through to SharedPointer::from_value, which calls Box::from_raw(ptr) with the null pointer. This triggers undefined behavior when utilizing safe deserialization APIs (such as rkyv::from_bytes or rkyv::deserialize_using) if an OOM condition occurs during the allocation of the shared pointer.

The issue is reachable through safe code and violates Rust's safety guarantees.