Deps.rs

topgrade 2.8.0

[![dependency status](https://deps.rs/crate/topgrade/2.8.0/status.svg)](https://deps.rs/crate/topgrade/2.8.0)

This project contains known security vulnerabilities. Find detailed information at the bottom.

Crate topgrade

Dependencies

(23 total, 13 outdated, 1 insecure)

CrateRequiredLatestStatus
 chrono^0.4.60.4.45up to date
 console^0.7.50.16.6out of date
 directories^2.0.16.0.0out of date
 failure^0.1.50.1.8up to date
 failure_derive^0.1.50.1.8up to date
 futures^0.1.270.3.34out of date
 glob^0.3.00.3.4up to date
 lazy_static^1.3.01.5.1up to date
 log^0.4.60.4.34up to date
 nix^0.15.00.31.3out of date
 openssl-probe^0.1.20.2.1out of date
 pretty_env_logger^0.3.00.5.0out of date
 rust-ini^0.13.00.21.3out of date
 self_update^0.6.01.3.0out of date
 serde^1.0.921.0.229up to date
 shellexpand^1.0.03.1.2out of date
 structopt^0.2.160.3.26out of date
 tokio ⚠️^0.1.211.53.2insecure
 tokio-process^0.2.30.2.5up to date
 toml^0.5.11.1.6+spec-1.1.0out of date
 walkdir^2.2.72.5.0up to date
 which^2.0.18.0.6out of date
 winapi^0.30.3.9up to 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.