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.
calamine(10 total, 1 outdated, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| atoi_simd | ^0.16 | 0.16.0 | up to date |
| byteorder | ^1.5 | 1.5.0 | up to date |
| chrono ⚠️ | ^0.4 | 0.4.41 | maybe insecure |
| codepage | ^0.1.1 | 0.1.2 | up to date |
| encoding_rs | ^0.8 | 0.8.35 | up to date |
| fast-float2 ⚠️ | ^0.2 | 0.2.3 | maybe insecure |
| log | ^0.4 | 0.4.27 | up to date |
| quick-xml | ^0.37 | 0.37.5 | up to date |
| serde | ^1.0 | 1.0.219 | up to date |
| zip | ~2.5.0 | 2.6.1 | out of date |
(5 total, 1 outdated)
| Crate | Required | Latest | Status |
|---|---|---|---|
| env_logger | ^0.11 | 0.11.8 | up to date |
| glob | ^0.3 | 0.3.2 | up to date |
| rstest | ^0.21.0 | 0.25.0 | out of date |
| serde_derive | ^1.0 | 1.0.219 | up to date |
| sha2 | ^0.10.8 | 0.10.9 | 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.
fast-float2: Segmentation fault due to lack of bound checkIn this case, the "fast_float2::common::AsciiStr::first" method within the "AsciiStr" struct uses the unsafe keyword to reading from memory without performing bounds checking. Specifically, it directly dereferences a pointer offset by "self.ptr". Because of the above reason, the method accesses invalid memory address when it takes an empty string as its input. This approach violates Rust’s memory safety guarantees, as it can lead to invalid memory access if empty buffer is provided.