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.
polars-ops(32 total, 3 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| ahash | >=0.8.5 | 0.8.11 | up to date |
| aho-corasick | ^1.1 | 1.1.3 | up to date |
| argminmax | ^0.6.2 | 0.6.2 | up to date |
| polars-arrow | ^0.46.0 | 0.46.0 | up to date |
| base64 | ^0.22.0 | 0.22.1 | up to date |
| bytemuck | ^1.21 | 1.22.0 | up to date |
| chrono | ^0.4.31 | 0.4.40 | up to date |
| chrono-tz | ^0.10 | 0.10.1 | up to date |
| either | ^1.11 | 1.15.0 | up to date |
| hashbrown ⚠️ | ^0.15.0 | 0.15.2 | maybe insecure |
| hex | ^0.4.3 | 0.4.3 | up to date |
| indexmap | ^2 | 2.8.0 | up to date |
| jsonpath_lib_polars_vendor | ^0.0.1 | 0.0.1 | up to date |
| memchr | ^2.6 | 2.7.4 | up to date |
| num-traits | ^0.2 | 0.2.19 | up to date |
| once_cell | ^1 | 1.21.1 | up to date |
| polars-compute | ^0.46.0 | 0.46.0 | up to date |
| polars-core | ^0.46.0 | 0.46.0 | up to date |
| polars-error | ^0.46.0 | 0.46.0 | up to date |
| polars-json | ^0.46.0 | 0.46.0 | up to date |
| polars-schema | ^0.46.0 | 0.46.0 | up to date |
| polars-utils | ^0.46.0 | 0.46.0 | up to date |
| rand | ^0.8 | 0.9.0 | out of date |
| rand_distr | ^0.4 | 0.5.1 | out of date |
| rayon | ^1.9 | 1.10.0 | up to date |
| regex | ^1.9 | 1.11.1 | up to date |
| regex-syntax | ^0.8.5 | 0.8.5 | up to date |
| serde | ^1.0.188 | 1.0.219 | up to date |
| serde_json | ^1 | 1.0.140 | up to date |
| strum_macros | ^0.26 | 0.27.1 | out of date |
| unicode-normalization | ^0.1.24 | 0.1.24 | up to date |
| unicode-reverse | ^1.0.8 | 1.0.9 | up to date |
(1 total, 1 outdated)
| Crate | Required | Latest | Status |
|---|---|---|---|
| rand | ^0.8 | 0.9.0 | out of date |
hashbrown: Borsh serialization of HashMap is non-canonicalThe 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.