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 meilies

Dependencies

(3 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 bytes^0.4.121.8.0out of date
 subslice^0.2.20.2.3up to date
 tokio ⚠️^0.1.191.41.1out of date

Crate meilies-cli

Dependencies

(5 total, 3 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 futures^0.1.260.3.31out of date
 log^0.4.60.4.22up to date
 stderrlog^0.4.10.6.0out of date
 structopt^0.3.30.3.26up to date
 tokio ⚠️^0.1.191.41.1out of date

Crate meilies-client

Dependencies

(4 total, 3 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 futures^0.1.260.3.31out of date
 log^0.4.60.4.22up to date
 tokio ⚠️^0.1.191.41.1out of date
 tokio-retry^0.2.00.3.0out of date

Crate meilies-inspect

Dependencies

(5 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 futures^0.1.260.3.31out of date
 meilies^0.2.00.2.0up to date
 meilies-client^0.2.00.2.0up to date
 structopt^0.3.30.3.26up to date
 tokio ⚠️^0.1.191.41.1out of date

Crate meilies-server

Dependencies

(8 total, 5 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 env_logger^0.7.10.11.5out of date
 futures^0.1.260.3.31out of date
 log^0.4.60.4.22up to date
 sentry^0.17.00.34.0out of date
 sled^0.29.10.34.7out of date
 structopt^0.3.30.3.26up to date
 tokio ⚠️^0.1.191.41.1out of date
 vigil-reporter^1.1.11.3.0up to date

Crate meilies-transhumance

Dependencies

(5 total, 3 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 futures^0.1.260.3.31out of date
 log^0.4.60.4.22up to date
 stderrlog^0.4.10.6.0out of date
 structopt^0.3.30.3.26up to date
 tokio ⚠️^0.1.191.41.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.