Deps.rs

mwalib 1.8.5

[![dependency status](https://deps.rs/crate/mwalib/1.8.5/status.svg)](https://deps.rs/crate/mwalib/1.8.5)

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 mwalib

Dependencies

(19 total, 7 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^1.01.0.97up to date
 chrono^0.4.380.4.40up to date
 clap~4.14.5.34out of date
 env_logger~0.100.11.7out of date
 fitsio^0.21.60.21.7up to date
 fitsio-sys~0.50.5.5up to date
 lazy_static^1.51.5.0up to date
 libc~0.20.2.171up to date
 log~0.40.4.27up to date
 ndarray~0.160.16.1up to date
 num-derive~0.40.4.2up to date
 num-traits~0.20.2.19up to date
 numpy~0.230.24.0out of date
 pyo3 ⚠️~0.230.24.1out of date
 pyo3-stub-gen~0.60.7.0out of date
 pyo3-stub-gen-derive~0.60.7.0out of date
 rayon^1.101.10.0up to date
 regex^1.91.11.1up to date
 thiserror^1.02.0.12out of date

Dev dependencies

(3 total, all up-to-date)

CrateRequiredLatestStatus
 csv^1.31.3.1up to date
 float-cmp~0.100.10.0up to date
 tempdir~0.30.3.7up 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.