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 libriichi

Dependencies

(25 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^11.0.98up to date
 log^0.40.4.27up to date
 pyo3-log^0.120.12.3up to date
 serde_json^11.0.140up to date
 boomphf^0.60.6.0up to date
 byteorder^11.5.0up to date
 rayon^11.10.0up to date
 ndarray^0.160.16.1up to date
 numpy^0.230.24.0out of date
 serde_with^33.12.0up to date
 rand^0.90.9.0up to date
 rand_chacha^0.90.9.0up to date
 flate2^11.1.1up to date
 sha3^0.100.10.8up to date
 glob^0.30.3.2up to date
 derivative^22.2.0up to date
 ahash^0.80.8.11up to date
 parking_lot^0.120.12.3up to date
 crossbeam^0.80.8.4up to date
 pyo3 ⚠️^0.230.24.1out of date
 indicatif^0.170.17.11up to date
 tinyvec^11.9.0up to date
 serde^11.0.219up to date
 derive_more^22.0.1up to date
 mimalloc^0.10.1.46up to date

Dev dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 criterion^0.50.5.1up to date

Build dependencies

(1 total, 1 outdated)

CrateRequiredLatestStatus
 pyo3-build-config^0.230.24.1out of date

Crate exe-wrapper

Dependencies

(2 total, all up-to-date)

CrateRequiredLatestStatus
 anyhow^11.0.98up to date
 dunce^11.0.5up 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.