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 rustracer-core

Dependencies

(23 total, 6 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^11.0.82up to date
 approx^0.50.5.1up to date
 atomic^0.50.6.0out of date
 bitflags^12.5.0out of date
 byteorder^1.41.5.0up to date
 chrono ⚠️^0.40.4.38maybe insecure
 crossbeam^0.80.8.4up to date
 exr^1.31.72.0up to date
 image^0.240.25.1out of date
 indicatif^0.160.17.8out of date
 itertools^0.100.12.1out of date
 lazy_static^1.41.4.0up to date
 light_arena^1.0.11.0.1up to date
 log^0.40.4.21up to date
 ndarray^0.150.15.6up to date
 num^0.40.4.2up to date
 num_cpus^11.16.0up to date
 parking_lot^0.120.12.1up to date
 ply-rs^0.10.1.3up to date
 rayon^11.10.0up to date
 state^0.50.6.0out of date
 thread-id^44.2.1up to date
 nom^7.07.1.3up to date

Dev dependencies

(2 total, all up-to-date)

CrateRequiredLatestStatus
 rand^0.80.8.5up to date
 quickcheck^11.0.3up to date

Crate rustracer

Dependencies

(6 total, 3 outdated)

CrateRequiredLatestStatus
 anyhow^11.0.82up to date
 clap^3.24.5.4out of date
 indicatif^0.160.17.8out of date
 log^0.40.4.21up to date
 flexi_logger^0.220.28.0out of date
 num_cpus^11.16.0up to date

Security Vulnerabilities

chrono: Potential segfault in `localtime_r` invocations

RUSTSEC-2020-0159

Impact

Unix-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.

Workarounds

No workarounds are known.

References