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.
surrealdb(34 total, 4 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| arrayvec | ^0.7.6 | 0.7.6 | up to date |
| bincode | ^1.3.3 | 1.3.3 | up to date |
| async-channel | ^2.3.1 | 2.3.1 | up to date |
| chrono | ^0.4.38 | 0.4.39 | up to date |
| dmp | ^0.2.0 | 0.2.0 | up to date |
| futures | ^0.3.30 | 0.3.31 | up to date |
| geo | ^0.28.0 | 0.29.3 | out of date |
| indexmap | ^2.1.0 | 2.7.0 | up to date |
| native-tls | ^0.2.11 | 0.2.12 | up to date |
| path-clean | ^1.0.1 | 1.0.1 | up to date |
| pharos | ^0.5.3 | 0.5.3 | up to date |
| reblessive | ^0.4.1 | 0.4.2 | up to date |
| reqwest | ^0.12.7 | 0.12.10 | up to date |
| revision | ^0.10.0 | 0.10.0 | up to date |
| ring | ^0.17.7 | 0.17.8 | up to date |
| rust_decimal | ^1.36.0 | 1.36.0 | up to date |
| rustls ⚠️ | ^0.23.12 | 0.23.20 | maybe insecure |
| rustls-pki-types | ^1.7.0 | 1.10.1 | up to date |
| semver | ^1.0.20 | 1.0.24 | up to date |
| serde | ^1.0.209 | 1.0.216 | up to date |
| serde-content | ^0.1.0 | 0.1.0 | up to date |
| serde_json | ^1.0.127 | 1.0.134 | up to date |
| surrealdb-core | =2.1.4 | 2.1.4 | up to date |
| thiserror | ^1.0.63 | 2.0.9 | out of date |
| tokio | ^1.40.0 | 1.42.0 | up to date |
| tokio-tungstenite | ^0.23.1 | 0.26.1 | out of date |
| tokio-util | ^0.7.11 | 0.7.13 | up to date |
| tracing | ^0.1.40 | 0.1.41 | up to date |
| trice | ^0.4.0 | 0.4.0 | up to date |
| url | ^2.5.0 | 2.5.4 | up to date |
| uuid | ^1.10.0 | 1.11.0 | up to date |
| wasm-bindgen-futures | ^0.4.39 | 0.4.49 | up to date |
| wasmtimer | ^0.2.0 | 0.4.1 | out of date |
| ws_stream_wasm | ^0.7.4 | 0.7.4 | up to date |
(17 total, 3 outdated)
| Crate | Required | Latest | Status |
|---|---|---|---|
| ciborium | ^0.2.1 | 0.2.2 | up to date |
| criterion | ^0.5.1 | 0.5.1 | up to date |
| env_logger | ^0.10.1 | 0.11.6 | out of date |
| flate2 | ^1.0.28 | 1.0.35 | up to date |
| hashbrown | ^0.14.5 | 0.15.2 | out of date |
| pprof | ^0.14.0 | 0.14.0 | up to date |
| radix_trie | ^0.2.1 | 0.2.1 | up to date |
| rand | ^0.8.5 | 0.8.5 | up to date |
| regex | ^1.10.6 | 1.11.1 | up to date |
| serial_test | ^2.0.0 | 3.2.0 | out of date |
| temp-dir | ^0.1.11 | 0.1.14 | up to date |
| test-log | ^0.2.13 | 0.2.16 | up to date |
| time | ^0.3.36 | 0.3.37 | up to date |
| tokio | ^1.40.0 | 1.42.0 | up to date |
| tracing-subscriber | ^0.3.18 | 0.3.19 | up to date |
| ulid | ^1.1.0 | 1.1.3 | up to date |
| wiremock | ^0.6.0 | 0.6.2 | up to date |
rustls: rustls network-reachable panic in `Acceptor::accept`A bug introduced in rustls 0.23.13 leads to a panic if the received
TLS ClientHello is fragmented. Only servers that use
rustls::server::Acceptor::accept() are affected.
Servers that use tokio-rustls's LazyConfigAcceptor API are affected.
Servers that use tokio-rustls's TlsAcceptor API are not affected.
Servers that use rustls-ffi's rustls_acceptor_accept API are affected.