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-utils(18 total, 5 outdated, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| ahash | >=0.8.5 | 0.8.11 | up to date |
| bytemuck | ^1.11 | 1.22.0 | up to date |
| bytes | ^1.7 | 1.10.1 | up to date |
| compact_str | ^0.8.0 | 0.9.0 | out of date |
| hashbrown ⚠️ | ^0.15.0 | 0.15.2 | maybe insecure |
| indexmap | ^2 | 2.8.0 | up to date |
| libc | ^0.2 | 0.2.171 | up to date |
| memmap2 | ^0.9 | 0.9.5 | up to date |
| num-traits | ^0.2 | 0.2.19 | up to date |
| once_cell | ^1 | 1.21.3 | up to date |
| polars-error | ^0.45.1 | 0.46.0 | out of date |
| pyo3 ⚠️ | ^0.22 | 0.24.1 | out of date |
| rand | ^0.8 | 0.9.0 | out of date |
| raw-cpuid | ^11 | 11.5.0 | up to date |
| rayon | ^1.9 | 1.10.0 | up to date |
| serde | ^1.0.188 | 1.0.219 | up to date |
| stacker | ^0.1 | 0.1.20 | up to date |
| sysinfo | ^0.32 | 0.34.1 | out of 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.
pyo3: Risk of buffer overflow in `PyString::from_object`PyString::from_object took &str arguments and forwarded them directly to the Python C API without checking for terminating nul bytes. This could lead the Python interpreter to read beyond the end of the &str data and potentially leak contents of the out-of-bounds read (by raising a Python exception containing a copy of the data including the overflow).
In PyO3 0.24.1 this function will now allocate a CString to guarantee a terminating nul bytes. PyO3 0.25 will likely offer an alternative API which takes &CStr arguments.