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.
asap(12 total, 3 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| bytes | ^1.1.0 | 1.6.0 | up to date |
| chrono ⚠️ | ^0.4 | 0.4.38 | maybe insecure |
| anyhow | ^1.0 | 1.0.82 | up to date |
| thiserror | ^1.0 | 1.0.59 | up to date |
| jsonwebtoken | ^7.2.0 | 9.3.0 | out of date |
| lru_time_cache | ^0.11.11 | 0.11.11 | up to date |
| pem | ^1.0.2 | 3.0.4 | out of date |
| rand | ^0.8.4 | 0.8.5 | up to date |
| reqwest | ^0.11.9 | 0.12.4 | out of date |
| serde | ^1.0.136 | 1.0.198 | up to date |
| serde_derive | ^1.0.136 | 1.0.198 | up to date |
| serde_json | ^1.0.78 | 1.0.116 | up to date |
(3 total, 1 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| base64 | ^0.13.0 | 0.22.0 | out of date |
| bencher | ^0.1.5 | 0.1.5 | up to date |
| tokio ⚠️ | ^1.16.1 | 1.37.0 | maybe insecure |
asap_deps_keyserver(3 total, 2 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| hyper | ^0.14.16 | 1.3.1 | out of date |
| reqwest | ^0.11.9 | 0.12.4 | out of date |
| tokio ⚠️ | ^1.16.1 | 1.37.0 | maybe insecure |
asap_cli(9 total, 4 outdated)
| Crate | Required | Latest | Status |
|---|---|---|---|
| clap | ^3.0.14 | 4.5.4 | out of date |
| directories | ^4.0.1 | 5.0.1 | out of date |
| human-panic | ^1.0.3 | 2.0.0 | out of date |
| anyhow | ^1.0 | 1.0.82 | up to date |
| thiserror | ^1.0 | 1.0.59 | up to date |
| pem | ^1.0.2 | 3.0.4 | out of date |
| serde | ^1.0.136 | 1.0.198 | up to date |
| serde_json | ^1.0.78 | 1.0.116 | up to date |
| serde_derive | ^1.0.136 | 1.0.198 | 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);