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.
arrow(23 total, 12 outdated, 3 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| ahash | ^0.7 | 0.8.12 | out of date |
| bitflags | ^1.2.1 | 2.9.1 | out of date |
| chrono ⚠️ | ^0.4 | 0.4.41 | maybe insecure |
| chrono-tz | ^0.6 | 0.10.3 | out of date |
| comfy-table | ^6.0 | 7.1.4 | out of date |
| csv | ^1.1 | 1.3.1 | up to date |
| flatbuffers ⚠️ | ^2.1.2 | 25.2.10 | out of date |
| half | ^2.0 | 2.6.0 | up to date |
| hashbrown | ^0.12 | 0.15.4 | out of date |
| hex | ^0.4 | 0.4.3 | up to date |
| indexmap | ^1.9 | 2.10.0 | out of date |
| lazy_static | ^1.4 | 1.5.0 | up to date |
| lexical-core | ^0.8 | 1.0.5 | out of date |
| multiversion | ^0.6.1 | 0.8.0 | out of date |
| num | ^0.4 | 0.4.3 | up to date |
| packed_simd_2 | ^0.3 | 0.3.8 | up to date |
| pyo3 ⚠️ | ^0.16 | 0.25.1 | out of date |
| rand | ^0.8 | 0.9.1 | out of date |
| regex | ^1.5.6 | 1.11.1 | up to date |
| regex-syntax | ^0.6.27 | 0.8.5 | out of date |
| serde | ^1.0 | 1.0.219 | up to date |
| serde_derive | ^1.0 | 1.0.219 | up to date |
| serde_json | ^1.0 | 1.0.140 | up to date |
(4 total, 2 outdated)
| Crate | Required | Latest | Status |
|---|---|---|---|
| criterion | ^0.3 | 0.6.0 | out of date |
| flate2 | ^1 | 1.1.2 | up to date |
| rand | ^0.8 | 0.9.1 | out of date |
| tempfile | ^3 | 3.20.0 | up to date |
chrono: Potential segfault in `localtime_r` invocationsUnix-like operating systems may segfault due to dereferencing a dangling pointer in specific circumstances. This requires an environment variable to be set in a different thread than the affected functions. This may occur without the user's knowledge, notably in a third-party library.
No workarounds are known.
flatbuffers: Generated code can read and write out of bounds in safe codeCode generated by flatbuffers' compiler is unsafe but not marked as such.
See https://github.com/google/flatbuffers/issues/6627 for details.
For example, if generated code is used to decode malformed or untrusted input,
undefined behavior (and thus security vulnerabilities) is possible even without
the use of the unsafe keyword, violating the the meaning of "safe" code;
All users that use generated code by flatbuffers compiler are recommended to:
follow, push, or any method that uses them
(e.g. self_follow).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.