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 metrics-util

Dependencies

(13 total, 3 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 ahash^0.80.8.11up to date
 aho-corasick^11.1.3up to date
 crossbeam-epoch^0.90.9.18up to date
 crossbeam-utils^0.80.8.21up to date
 hashbrown ⚠️^0.150.15.2maybe insecure
 indexmap^2.62.7.1up to date
 metrics^0.240.24.1up to date
 ordered-float^4.25.0.0out of date
 quanta^0.120.12.5up to date
 radix_trie^0.20.2.1up to date
 rand^0.80.9.0out of date
 rand_xoshiro^0.60.7.0out of date
 sketches-ddsketch^0.30.3.0up to date

Dev dependencies

(20 total, 8 outdated)

CrateRequiredLatestStatus
 approx^0.50.5.1up to date
 criterion=0.3.30.5.1out of date
 crossbeam-queue^0.30.3.12up to date
 getopts^0.20.2.21up to date
 hdrhistogram^7.27.5.4up to date
 mockall^0.120.13.1out of date
 ndarray^0.160.16.1up to date
 ndarray-stats^0.60.6.0up to date
 noisy_float^0.20.2.0up to date
 ordered-float^4.25.0.0out of date
 predicates=3.1.03.1.3out of date
 predicates-core=1.0.61.0.9out of date
 predicates-tree=1.0.91.0.12out of date
 quickcheck^11.0.3up to date
 quickcheck_macros^11.0.0up to date
 rand^0.80.9.0out of date
 rand_distr^0.40.5.1out of date
 sketches-ddsketch^0.30.3.0up to date
 tracing^0.10.1.41up to date
 tracing-subscriber^0.30.3.19up to date

Security Vulnerabilities

hashbrown: Borsh serialization of HashMap is non-canonical

RUSTSEC-2024-0402

The borsh serialization of the HashMap did not follow the borsh specification. It potentially produced non-canonical encodings dependent on insertion order. It also did not perform canonicty checks on decoding.

This can result in consensus splits and cause equivalent objects to be considered distinct.

This was patched in 0.15.1.