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 eszip

Dependencies

(11 total, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^11.0.65up to date
 base64^0.13.00.13.0up to date
 deno_ast^0.19.00.19.0up to date
 deno_graph^0.34.00.34.0up to date
 futures^0.3.190.3.24up to date
 serde^11.0.145up to date
 serde_json^11.0.85up to date
 sha2^0.10.10.10.6up to date
 thiserror^1.0.301.0.37up to date
 tokio ⚠️^11.21.2maybe insecure
 url^2.2.22.3.1up to date

Dev dependencies

(3 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 import_map^0.7.00.12.1out of date
 pretty_assertions^11.3.0up to date
 tokio ⚠️^11.21.2maybe insecure

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.