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 tame-index

Dependencies

(19 total, 3 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 bytes^1.41.6.0up to date
 camino^1.11.1.6up to date
 crossbeam-channel^0.50.5.12up to date
 gix^0.580.62.0out of date
 home^0.50.5.9up to date
 http^0.21.1.0out of date
 libc^0.20.2.153up to date
 memchr^2.52.7.2up to date
 rayon^1.71.10.0up to date
 reqwest^0.110.12.4out of date
 semver^1.01.0.22up to date
 serde^1.01.0.199up to date
 serde_json^1.01.0.116up to date
 sha2^0.100.10.8up to date
 smol_str^0.2.00.2.1up to date
 thiserror^1.01.0.59up to date
 tokio ⚠️^1.01.37.0maybe insecure
 toml-span^0.20.2.0up to date
 twox-hash^1.61.6.3up to date

Dev dependencies

(4 total, all up-to-date)

CrateRequiredLatestStatus
 cargo_metadata^0.180.18.1up to date
 rayon^1.71.10.0up to date
 tempfile^3.63.10.1up to date
 tiny-bench^0.30.3.0up 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);