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 overlord

Dependencies

(18 total, 10 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-trait^0.10.1.88up to date
 bit-vec^0.60.8.0out of date
 bytes^0.51.10.1out of date
 creep^0.20.3.0out of date
 derive_more^0.992.0.1out of date
 futures^0.30.3.31up to date
 futures-timer^3.03.0.3up to date
 hex^0.40.4.3up to date
 log^0.40.4.27up to date
 moodyblues-sdk^0.30.3.0up to date
 parking_lot^0.100.12.4out of date
 prime_tools^0.20.3.4out of date
 rand_core^0.50.9.3out of date
 rand_pcg^0.20.9.0out of date
 rlp^0.40.6.1out of date
 serde^1.01.0.219up to date
 serde_json^1.01.0.140up to date
 tokio ⚠️^0.21.46.1out of date

Dev dependencies

(7 total, 5 outdated)

CrateRequiredLatestStatus
 bincode^1.22.0.1out of date
 blake2b_simd^0.51.0.3out of date
 crossbeam-channel^0.40.5.15out of date
 env_logger^0.70.11.8out of date
 hasher^0.10.1.4up to date
 lazy_static^1.41.5.0up to date
 rand^0.70.9.1out of date

Security Vulnerabilities

tokio: Data race when sending and receiving after closing a `oneshot` channel

RUSTSEC-2021-0124

If a tokio::sync::oneshot channel is closed (via the oneshot::Receiver::close method), a data race may occur if the oneshot::Sender::send method is called while the corresponding oneshot::Receiver is awaited or calling try_recv.

When these methods are called concurrently on a closed channel, the two halves of the channel can concurrently access a shared memory location, resulting in a data race. This has been observed to cause memory corruption.

Note that the race only occurs when both halves of the channel are used after the Receiver half has called close. Code where close is not used, or where the Receiver is not awaited and try_recv is not called after calling close, is not affected.

See tokio#4225 for more details.