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.
threatflux(21 total, 5 outdated, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| reqwest | ^0.11 | 0.12.23 | out of date |
| tokio ⚠️ | ^1.0 | 1.47.1 | maybe insecure |
| serde | ^1.0 | 1.0.219 | up to date |
| serde_json | ^1.0 | 1.0.143 | up to date |
| thiserror | ^1.0 | 2.0.16 | out of date |
| anyhow | ^1.0 | 1.0.99 | up to date |
| dotenv | ^0.15 | 0.15.0 | up to date |
| tracing | ^0.1 | 0.1.41 | up to date |
| tracing-subscriber | ^0.3 | 0.3.20 | up to date |
| url | ^2.4 | 2.5.7 | up to date |
| base64 | ^0.21 | 0.22.1 | out of date |
| uuid | ^1.0 | 1.18.1 | up to date |
| chrono ⚠️ | ^0.4 | 0.4.41 | maybe insecure |
| futures | ^0.3 | 0.3.31 | up to date |
| tokio-stream | ^0.1 | 0.1.17 | up to date |
| backoff | ^0.4 | 0.4.0 | up to date |
| governor | ^0.5 | 0.10.1 | out of date |
| nonzero_ext | ^0.3 | 0.3.0 | up to date |
| http | ^0.2 | 1.3.1 | out of date |
| mime | ^0.3 | 0.3.17 | up to date |
| mime_guess | ^2.0 | 2.0.5 | up to date |
(9 total, 1 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| tokio-test | ^0.4 | 0.4.4 | up to date |
| mockito | ^1.0 | 1.7.0 | up to date |
| tempfile | ^3.0 | 3.21.0 | up to date |
| wiremock | ^0.5 | 0.6.5 | out of date |
| pretty_assertions | ^1.4 | 1.4.1 | up to date |
| serde_json | ^1.0 | 1.0.143 | up to date |
| tokio ⚠️ | ^1.0 | 1.47.1 | maybe insecure |
| futures-util | ^0.3 | 0.3.31 | up to date |
| async-std | ^1.12 | 1.13.2 | up to date |
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);