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 bilrost

Dependencies

(12 total, 1 possibly insecure)

CrateRequiredLatestStatus
 arrayvec>=0.60.7.6up to date
 bstr>=11.11.3up to date
 bytes^11.9.0up to date
 bytestring>=11.4.0up to date
 chrono>=0.4.340.4.39up to date
 const_panic^0.20.2.12up to date
 hashbrown ⚠️>=0.1.00.15.2maybe insecure
 smallvec>=1.6.11.13.2up to date
 thin-vec>=0.20.2.13up to date
 time>=0.3.00.3.37up to date
 tinyvec>=11.8.1up to date
 pprof>=0.13, <0.150.14.0up to date

Dev dependencies

(10 total, 1 outdated)

CrateRequiredLatestStatus
 arbitrary^1.41.4.1up to date
 chrono>=0.4.340.4.39up to date
 criterion^0.50.5.1up to date
 hashbrown>=0.15.20.15.2up to date
 itertools^0.140.14.0up to date
 proptest^11.6.0up to date
 rand^0.80.9.0out of date
 static_assertions^11.1.0up to date
 time>=0.3.00.3.37up to date
 yoke^0.7.10.7.5up to date

Crate bilrost-derive

Dependencies

(5 total, all up-to-date)

CrateRequiredLatestStatus
 eyre^0.6.120.6.12up to date
 itertools^0.140.14.0up to date
 proc-macro2^11.0.93up to date
 quote^11.0.38up to date
 syn^22.0.98up to date

Crate bilrost-types

Dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 serde_json^11.0.138up to date

Dev dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 proptest^11.6.0up to date

Crate common

Dependencies

(9 total, all up-to-date)

CrateRequiredLatestStatus
 bstr^1.101.11.3up to date
 bytes^11.9.0up to date
 bytestring^1.3.11.4.0up to date
 chrono^0.4.340.4.39up to date
 eyre^0.6.120.6.12up to date
 once_cell^1.20.21.20.2up to date
 regex^1.111.11.1up to date
 time^0.30.3.37up to date
 tinyvec^11.8.1up 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.