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 spirit-tokio

Dependencies

(15 total, 6 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 either~11.11.0up to date
 failure~0.10.1.8up to date
 futures~0.10.3.30out of date
 humantime~12.1.0out of date
 log~0.40.4.21up to date
 net2~0.20.2.39up to date
 parking_lot~0.70.12.2out of date
 serde~11.0.200up to date
 serde-humantime~0.10.1.1up to date
 serde_derive~11.0.200up to date
 spirit~0.3.60.4.21out of date
 structdoc~0.10.1.4up to date
 structopt~0.20.3.26out of date
 tk-listen~0.20.2.1up to date
 tokio ⚠️~0.1.81.37.0out of date

Dev dependencies

(4 total, 2 outdated)

CrateRequiredLatestStatus
 corona~0.4.10.4.3up to date
 env_logger~0.60.11.3out of date
 serde_json~11.0.116up to date
 version-sync~0.70.9.5out 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.