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.
mc-crawler(10 total, 4 outdated, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| grpcio | ^0.10.2 | 0.13.0 | out of date |
| log | ^0.4 | 0.4.29 | up to date |
| env_logger | ^0.10 | 0.11.8 | out of date |
| url | ^2.5 | 2.5.8 | up to date |
| serde | ^1.0 | 1.0.228 | up to date |
| serde_json | ^1.0 | 1.0.149 | up to date |
| chrono ⚠️ | ^0.4 | 0.4.42 | maybe insecure |
| base64 | ^0.21 | 0.22.1 | out of date |
| structopt | ^0.3 | 0.3.26 | up to date |
| maxminddb ⚠️ | ^0.24 | 0.27.1 | out of date |
(2 total, 1 outdated)
| Crate | Required | Latest | Status |
|---|---|---|---|
| assert_cmd | ^2.0 | 2.1.2 | up to date |
| predicates | ^2.1.5 | 3.1.3 | out of 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.
maxminddb: `Reader::open_mmap` unsoundly marks unsafe memmap operation as safemaxminddb prior to version 0.27 declared Reader::open_mmap as safe
despite wrapping an inherently unsafe memmap2 operation with no
extra step done to guarantee safety. This could have led to undefined
behaviour if the file were to be modified on disk while the memory map
was still active.