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.
pleco_engine(5 total, 2 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| chrono ⚠️ | ^0.4.6 | 0.4.38 | maybe insecure |
| num_cpus | ^1.8.0 | 1.16.0 | up to date |
| pleco | ^0.4.4 | 0.5.0 | out of date |
| prefetch | ^0.2.0 | 0.2.0 | up to date |
| rand | ^0.6.5 | 0.8.5 | out of date |
(2 total, 1 outdated)
| Crate | Required | Latest | Status |
|---|---|---|---|
| criterion | ^0.2.10 | 0.5.1 | out of date |
| lazy_static | ^1.3.0 | 1.4.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.