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 orientdb-client


(11 total, 2 outdated, 2 possibly insecure)

 chrono ⚠️^ insecure
 byteorder^ to date
 r2d2^ to date
 nom^ of date
 thiserror^ to date
 async-std^ to date
 async-trait^ to date
 futures^ to date
 mobc^ to date
 tokio ⚠️^11.21.2maybe insecure
 uuid^ of date

Dev dependencies

(2 total, 2 outdated)

 dotenv^ of date
 uuid^ of date

Crate orientdb-macro


(3 total, all up-to-date)

 proc-macro2^ to date
 syn^ to date
 quote^ to date

Security Vulnerabilities

chrono: Potential segfault in `localtime_r` invocations



Unix-like operating systems may segfault due to dereferencing a dangling pointer in specific circumstances. This requires an environment variable to be set in a different thread than the affected functions. This may occur without the user's knowledge, notably in a third-party library.


No workarounds are known.


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


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.