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.
deno_cache_dir(25 total, 4 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| async-trait | ^0.1.73 | 0.1.85 | up to date |
| base32 | =0.5.1 | 0.5.1 | up to date |
| base64 | ^0.21.7 | 0.22.1 | out of date |
| boxed_error | ^0.2.3 | 0.2.3 | up to date |
| cache_control | ^0.2.0 | 0.2.0 | up to date |
| chrono ⚠️ | ^0.4 | 0.4.39 | maybe insecure |
| console_error_panic_hook | ^0.1.6 | 0.1.7 | up to date |
| data-url | ^0.3.0 | 0.3.1 | up to date |
| deno_error | ^0.5.2 | 0.5.5 | up to date |
| deno_media_type | ^0.2.2 | 0.2.3 | up to date |
| deno_path_util | ^0.3.0 | 0.3.0 | up to date |
| http | ^1 | 1.2.0 | up to date |
| indexmap | ^2.0.0 | 2.7.0 | up to date |
| js-sys | =0.3.68 | 0.3.77 | out of date |
| log | ^0.4.19 | 0.4.25 | up to date |
| once_cell | ^1.18.0 | 1.20.2 | up to date |
| parking_lot | ^0.12.1 | 0.12.3 | up to date |
| serde | ^1.0.183 | 1.0.217 | up to date |
| serde-wasm-bindgen | ^0.6.5 | 0.6.5 | up to date |
| serde_json | ^1.0.104 | 1.0.135 | up to date |
| sha2 | ^0.10.0 | 0.10.8 | up to date |
| sys_traits | ^0.1.0 | 0.1.7 | up to date |
| thiserror | ^1.0.44 | 2.0.11 | out of date |
| url | ^2.5.1 | 2.5.4 | up to date |
| wasm-bindgen | =0.2.91 | 0.2.100 | out of date |
(4 total, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| pretty_assertions | ^1.4.0 | 1.4.1 | up to date |
| sys_traits | ^0.1.0 | 0.1.7 | up to date |
| tempfile | ^3.7.1 | 3.15.0 | up to date |
| tokio ⚠️ | ^1 | 1.43.0 | maybe insecure |
chrono: Potential segfault in `localtime_r` invocationsUnix-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: reject_remote_clients Configuration corruptionOn Windows, configuring a named pipe server with pipe_mode will force ServerOptions::reject_remote_clients as false.
This drops any intended explicit configuration for the reject_remote_clients that may have been set as true previously.
The default setting of reject_remote_clients is normally true meaning the default is also overridden as false.
Ensure that pipe_mode is set first after initializing a ServerOptions. For example:
let mut opts = ServerOptions::new();
opts.pipe_mode(PipeMode::Message);
opts.reject_remote_clients(true);