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 polars-arrow

Dependencies

(27 total, 3 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 polars-arrow-format^0.1.00.2.0out of date
 async-stream^0.30.3.6up to date
 atoi_simd^0.160.16.1up to date
 avro-schema^0.30.3.0up to date
 bitflags^22.9.1up to date
 bytemuck^1.221.23.1up to date
 chrono^0.4.310.4.41up to date
 chrono-tz^0.100.10.3up to date
 dyn-clone^11.0.19up to date
 either^1.141.15.0up to date
 ethnum^1.3.21.5.2up to date
 futures^0.3.250.3.31up to date
 getrandom^0.20.3.3out of date
 hashbrown ⚠️^0.15.00.15.4maybe insecure
 itoa^1.0.61.0.15up to date
 lz4^1.241.28.1up to date
 num-traits^0.20.2.19up to date
 polars-error^0.48.10.48.1up to date
 polars-schema^0.48.10.48.1up to date
 polars-utils^0.48.10.48.1up to date
 proptest^1.61.7.0up to date
 serde^1.0.1881.0.219up to date
 simdutf8^0.1.40.1.5up to date
 streaming-iterator^0.1.90.1.9up to date
 strum_macros^0.260.27.1out of date
 tokio^1.441.45.1up to date
 zstd^0.130.13.3up to date

Dev dependencies

(3 total, 1 outdated)

CrateRequiredLatestStatus
 proptest^1.61.7.0up to date
 rand^0.80.9.1out of date
 tokio^1.441.45.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.