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 common Dependencies (12 total, 2 outdated, 1 possibly insecure)
Crate ingestion Dependencies (13 total, 4 outdated, 1 possibly insecure)
Dev dependencies (1 total, all up-to-date)
Crate Required Latest Status tokio ^1.351.51.0up to date
Crate feature Dependencies (3 total, 1 outdated)
Crate Required Latest Status serde ^1.01.0.228up to date anyhow ^1.01.0.102up to date dashmap ^5.56.1.0out of date
Crate strategy Dependencies (3 total, all up-to-date)
Crate Required Latest Status serde ^1.01.0.228up to date anyhow ^1.01.0.102up to date tracing ^0.10.1.44up to date
Crate model Dependencies (2 total, all up-to-date)
Crate Required Latest Status anyhow ^1.01.0.102up to date tracing ^0.10.1.44up to date
Crate risk Dependencies (2 total, 1 outdated)
Crate daemon Dependencies (13 total, 2 outdated, 2 possibly insecure)
Crate event_bus Dependencies (7 total, all up-to-date)
Crate cli Dependencies (3 total, all up-to-date)
Crate Required Latest Status clap ^4.44.6.0up to date anyhow ^1.01.0.102up to date tokio ^1.351.51.0up to date
Crate tui Dependencies (11 total, 3 outdated)
Crate web Dependencies (7 total, 1 outdated, 2 possibly insecure)
Crate web-dashboard Dependencies (9 total, 2 outdated, 3 possibly insecure)
Crate dashboard Dependencies (7 total, 2 outdated, 1 possibly insecure)
Crate tests Dev dependencies (2 total, all up-to-date)
Crate Required Latest Status tokio ^1.351.51.0up to date anyhow ^1.01.0.102up to date
Crate persistence Dependencies (11 total, 4 outdated, 2 possibly insecure)
Crate ai Dependencies (10 total, 4 outdated, 1 possibly insecure)
Crate ml No external dependencies! 🙌
Crate backtest Dependencies (1 total, 1 possibly insecure)
Crate Required Latest Status chrono ⚠️ ^0.40.4.44maybe insecure
Crate compliance Dependencies (5 total, 2 outdated)
Crate execution Dependencies (4 total, 1 outdated)
Crate alerts Dependencies (5 total, 1 outdated, 1 possibly insecure)
Crate signals Dependencies (1 total, all up-to-date)
Crate Required Latest Status tracing ^0.10.1.44up to date
Crate pricing Dependencies (1 total, all up-to-date)
Crate Required Latest Status tracing ^0.10.1.44up to date
Crate metrics_lib Dependencies (3 total, 2 outdated)
Crate fix Dependencies (4 total, 1 outdated, 2 possibly insecure)
Crate oms No external dependencies! 🙌
Crate swarm_sim Dependencies (5 total, 3 outdated)
Crate Required Latest Status rayon ^1.101.11.0up to date rand ^0.80.10.0out of date anyhow ^1.01.0.102up to date rand_distr ^0.40.6.0out of date statrs ^0.160.18.0out of date
Dev dependencies (3 total, 1 outdated)
Crate knowledge_graph Dependencies (7 total, 1 outdated, 2 possibly insecure)
Crate polymarket Dependencies (15 total, 4 outdated)
Crate benchmarks Dev dependencies (7 total, 2 outdated)
Security Vulnerabilities chrono: Potential segfault in `localtime_r` invocationsRUSTSEC-2020-0159
Impact
Unix-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.
Workarounds
No workarounds are known.
References
tokio: reject_remote_clients Configuration corruptionRUSTSEC-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);
Patched
>=1.18.4, <1.19.0
>=1.20.3, <1.21.0
>=1.23.1
tracing-subscriber: Logging user input may result in poisoning logs with ANSI escape sequencesRUSTSEC-2025-0055
Previous versions of tracing-subscriber were vulnerable to ANSI escape sequence injection attacks. Untrusted user input containing ANSI escape sequences could be injected into terminal output when logged, potentially allowing attackers to:
Manipulate terminal title bars
Clear screens or modify terminal display
Potentially mislead users through terminal manipulation
In isolation, impact is minimal, however security issues have been found in terminal emulators that enabled an attacker to use ANSI escape sequences via logs to exploit vulnerabilities in the terminal emulator.
This was patched in PR #3368 to escape ANSI control characters from user input.