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.
curlz(20 total, 6 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| env_logger | ^0.10 | 0.11.3 | out of date |
| log | ^0.4 | 0.4.21 | up to date |
| clap | ^4.2 | 4.5.4 | up to date |
| clap-verbosity-flag | ^2.0 | 2.2.0 | up to date |
| serde | ^1.0 | 1.0.200 | up to date |
| serde_yaml | ^0.9 | 0.9.34+deprecated | up to date |
| dotenvy | ^0.15 | 0.15.7 | up to date |
| anyhow | ^1.0 | 1.0.82 | up to date |
| convert_case | ^0.6 | 0.6.0 | up to date |
| dialoguer | ^0.10 | 0.11.0 | out of date |
| filenamify | ^0.1 | 0.1.0 | up to date |
| chrono ⚠️ | ^0.4 | 0.4.38 | maybe insecure |
| humantime | ^2.1 | 2.1.0 | up to date |
| minijinja | ^0.32 | 2.0.1 | out of date |
| jsonwebtoken | ^8.3 | 9.3.0 | out of date |
| serde_json | ^1.0 | 1.0.116 | up to date |
| base64 | ^0.21 | 0.22.1 | out of date |
| pest | ^2.6 | 2.7.10 | up to date |
| pest_derive | ^2.6 | 2.7.10 | up to date |
| minijinja-stack-ref | ^0.32 | 1.0.21 | out of date |
(9 total, 2 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| insta | ^1 | 1.38.0 | up to date |
| tempfile | ^3.5 | 3.10.1 | up to date |
| assert_cmd | ^2.0 | 2.0.14 | up to date |
| predicates | ^3.0 | 3.1.0 | up to date |
| rstest | ^0.17 | 0.19.0 | out of date |
| wiremock | ^0.5 | 0.6.0 | out of date |
| tokio ⚠️ | ^1 | 1.37.0 | maybe insecure |
| indoc | ^2 | 2.0.5 | up to date |
| pretty_assertions | ^1 | 1.4.0 | 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);