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.
swgoh_farming_bot(16 total, 4 outdated, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| api-swgoh-gg | ^0.3 | 0.3.0 | up to date |
| dotenv | ^0.15 | 0.15.0 | up to date |
| env_logger | ^0.9 | 0.11.3 | out of date |
| lazy_static | ^1.4 | 1.4.0 | up to date |
| log | ^0.4 | 0.4.21 | up to date |
| numerals | ^0.1 | 0.1.4 | up to date |
| r2d2 | ^0.8.9 | 0.8.10 | up to date |
| serde_json | ^1.0 | 1.0.116 | up to date |
| time | ^0.3 | 0.3.36 | up to date |
| diesel_migrations | ^1.4 | 2.1.0 | out of date |
| tokio-stream | ^0.1 | 0.1.15 | up to date |
| tokio ⚠️ | ^1.16 | 1.37.0 | maybe insecure |
| serenity | ^0.10 | 0.12.1 | out of date |
| chrono ⚠️ | ^0.4 | 0.4.38 | maybe insecure |
| serde | ^1.0 | 1.0.198 | up to date |
| diesel | ^1.4.6 | 2.1.6 | out of 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);