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-core

Dependencies

(29 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 polars-arrow^0.50.00.50.0up to date
 bitflags^22.9.2up to date
 boxcar^0.2.120.2.14up to date
 bytemuck^1.221.23.2up to date
 chrono^0.4.310.4.41up to date
 chrono-tz^0.100.10.4up to date
 comfy-table^7.1.17.1.4up to date
 either^1.141.15.0up to date
 hashbrown ⚠️^0.15.00.15.5maybe insecure
 indexmap^22.10.0up to date
 itoa^1.0.61.0.15up to date
 ndarray^0.160.16.1up to date
 num-traits^0.20.2.19up to date
 polars-compute^0.50.00.50.0up to date
 polars-dtype^0.50.00.50.0up to date
 polars-error^0.50.00.50.0up to date
 polars-row^0.50.00.50.0up to date
 polars-schema^0.50.00.50.0up to date
 polars-utils^0.50.00.50.0up to date
 rand^0.90.9.2up to date
 rand_distr^0.50.5.1up to date
 rayon^1.91.11.0up to date
 regex^1.91.11.1up to date
 schemars^0.8.221.0.4out of date
 serde^1.0.1881.0.219up to date
 serde_json^11.0.143up to date
 strum_macros^0.270.27.2up to date
 uuid^1.15.11.18.0up to date
 xxhash-rust^0.8.60.8.15up to date

Dev dependencies

(2 total, all up-to-date)

CrateRequiredLatestStatus
 bincode^2.02.0.1up to date
 serde_json^11.0.143up 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.