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.
napi(12 total, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| anyhow | ^1 | 1.0.94 | up to date |
| bitflags | ^2 | 2.6.0 | up to date |
| chrono ⚠️ | ^0.4 | 0.4.39 | maybe insecure |
| ctor | ^0.2 | 0.2.9 | up to date |
| encoding_rs | ^0.8 | 0.8.35 | up to date |
| indexmap | ^2 | 2.7.0 | up to date |
| napi-derive | ^2.10.1 | 2.16.13 | up to date |
| napi-sys | ^2.4.0 | 2.4.0 | up to date |
| once_cell | ^1.19 | 1.20.2 | up to date |
| serde | ^1 | 1.0.216 | up to date |
| serde_json | ^1 | 1.0.133 | up to date |
| tokio ⚠️ | ^1 | 1.42.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);