Deps.rs

polars-lazy 0.45.1

[![dependency status](https://deps.rs/crate/polars-lazy/0.45.1/status.svg)](https://deps.rs/crate/polars-lazy/0.45.1)

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

Dependencies

(20 total, 13 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 ahash>=0.8.50.8.11up to date
 polars-arrow^0.45.10.46.0out of date
 bitflags^22.9.0up to date
 futures^0.3.250.3.31up to date
 memchr^2.62.7.4up to date
 once_cell^11.21.3up to date
 polars-core^0.45.10.46.0out of date
 polars-expr^0.45.10.46.0out of date
 polars-io^0.45.10.46.0out of date
 polars-json^0.45.10.46.0out of date
 polars-mem-engine^0.45.10.46.0out of date
 polars-ops^0.45.10.46.0out of date
 polars-pipe^0.45.10.46.0out of date
 polars-plan^0.45.10.46.0out of date
 polars-stream^0.45.10.46.0out of date
 polars-time^0.45.10.46.0out of date
 polars-utils^0.45.10.46.0out of date
 pyo3 ⚠️^0.220.24.1out of date
 rayon^1.91.10.0up to date
 tokio^1.261.44.1up to date

Dev dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 serde_json^11.0.140up to date

Security Vulnerabilities

pyo3: Risk of buffer overflow in `PyString::from_object`

RUSTSEC-2025-0020

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.