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

Dependencies

(29 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 polars-arrow^0.48.10.48.1up to date
 bitflags^22.9.1up to date
 bytemuck^1.221.23.1up to date
 bytes^1.101.10.1up to date
 chrono^0.4.310.4.41up to date
 chrono-tz^0.100.10.3up to date
 either^1.141.15.0up to date
 futures^0.3.250.3.31up to date
 hashbrown ⚠️^0.15.00.15.4maybe insecure
 libloading^0.8.00.8.8up to date
 memmap2^0.90.9.5up to date
 num-traits^0.20.2.19up to date
 percent-encoding^2.32.3.1up to date
 polars-compute^0.48.10.48.1up to date
 polars-core^0.48.10.48.1up to date
 polars-ffi^0.48.10.48.1up to date
 polars-io^0.48.10.48.1up to date
 polars-json^0.48.10.48.1up to date
 polars-ops^0.48.10.48.1up to date
 polars-parquet^0.48.10.48.1up to date
 polars-time^0.48.10.48.1up to date
 polars-utils^0.48.10.48.1up to date
 pyo3^0.24.20.25.1out of date
 rayon^1.91.10.0up to date
 recursive^0.10.1.1up to date
 regex^1.91.11.1up to date
 serde^1.0.1881.0.219up to date
 serde_json^11.0.140up to date
 strum_macros^0.260.27.1out of 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.