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 ollama-rs

Dependencies

(20 total, 4 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-stream^0.3.50.3.6up to date
 calc^0.4.00.5.0out of date
 html2md^0.2.150.2.15up to date
 http^1.3.11.4.0up to date
 log^0.40.4.29up to date
 modelfile^0.3.10.3.1up to date
 ollama-rs-macros^0.3.30.3.3up to date
 regex^1.12.21.12.3up to date
 reqwest^0.12.240.13.1out of date
 schemars^1.0.41.2.1up to date
 scraper^0.24.00.25.0out of date
 serde^11.0.228up to date
 serde_json^11.0.149up to date
 serde_with^3.16.03.16.1up to date
 static_assertions^1.1.01.1.0up to date
 text-splitter^0.28.00.29.3out of date
 thiserror^2.0.172.0.18up to date
 tokio ⚠️^11.49.0maybe insecure
 tokio-stream^0.1.170.1.18up to date
 url^22.5.8up to date

Dev dependencies

(5 total, 1 possibly insecure)

CrateRequiredLatestStatus
 base64^0.22.10.22.1up to date
 fs2^0.4.30.4.3up to date
 futures-util^0.30.3.31up to date
 tokio ⚠️^11.49.0maybe insecure
 tokio-stream^0.1.170.1.18up 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);