Deps.rs

babycat-io / babycat

[![dependency status](https://deps.rs/repo/github/babycat-io/babycat/status.svg)](https://deps.rs/repo/github/babycat-io/babycat)

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 babycat

Dependencies

(20 total, 8 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 symphonia^0.5.20.5.4up to date
 base64^0.130.22.1out of date
 float-cmp^0.90.10.0out of date
 hound^3.43.5.1up to date
 humantime^2.12.2.0up to date
 either^1.61.15.0up to date
 serde^1.01.0.219up to date
 serde_json^1.01.0.140up to date
 log^0.40.4.27up to date
 rayon^1.6.11.10.0up to date
 samplerate^0.2.40.2.4up to date
 wasm-bindgen^0.20.2.100up to date
 js-sys^0.30.3.77up to date
 numpy^0.18.00.24.0out of date
 pyo3 ⚠️^0.18.10.24.1out of date
 env_logger^0.90.11.8out of date
 structopt^0.30.3.26up to date
 rodio^0.150.20.1out of date
 crossterm^0.230.29.0out of date
 ffmpeg-next^5.1.17.1.0out of date

Dev dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 wasm-bindgen-test^0.30.3.50up 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.