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.

Crate odin

Dependencies

(29 total, 1 possibly insecure)

CrateRequiredLatestStatus
 handlebars^6.3.26.3.2up to date
 dotenv^0.150.15.0up to date
 log^0.4.270.4.27up to date
 clap^4.5.364.5.38up to date
 which*7.0.3up to date
 serde^1.0.2191.0.219up to date
 sysinfo^0.35.00.35.1up to date
 serde_json^1.0.1401.0.140up to date
 daemonize^0.5.00.5.0up to date
 tar^0.4.440.4.44up to date
 flate2^1.1.11.1.1up to date
 inflections^1.1.11.1.1up to date
 md5^0.70.7.0up to date
 reqwest^0.12.150.12.15up to date
 chrono^0.4.400.4.41up to date
 zip^2.6.12.6.1up to date
 fs_extra^1.31.3.0up to date
 glob^0.30.3.2up to date
 a2s^0.5.20.5.2up to date
 serde_with^3.12.03.12.0up to date
 regex^1.11.11.11.1up to date
 tokio ⚠️^11.45.0maybe insecure
 notify^8.0.08.0.0up to date
 json-patch*4.0.0up to date
 cached^00.55.1up to date
 anyhow^1.0.981.0.98up to date
 thiserror^2.0.122.0.12up to date
 tempfile^3.19.13.20.0up to date
 walkdir^2.5.02.5.0up to date

Dev dependencies

(8 total, all up-to-date)

CrateRequiredLatestStatus
 once_cell^1.21.31.21.3up to date
 rand^0.9.10.9.1up to date
 serial_test^3.2.03.2.0up to date
 mockito^1.7.01.7.0up to date
 lazy_static^1.5.01.5.0up to date
 test-case^33.3.1up to date
 mockall^00.13.1up to date
 cargo-husky^1.5.01.5.0up to date

Build dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 cc^11.2.22up to date

Crate huginn

Dependencies

(3 total, 1 possibly insecure)

CrateRequiredLatestStatus
 log^0.4.270.4.27up to date
 tokio ⚠️^11.45.0maybe insecure
 warp^0.3.70.3.7up to date

Dev dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 cargo-husky^1.5.01.5.0up to date

Build dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 cc^11.2.22up to date

Security Vulnerabilities

tokio: reject_remote_clients Configuration corruption

RUSTSEC-2023-0001

On 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.

Workarounds

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);