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 okh-scraper

Dependencies

(32 total, 3 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 async-std^1.131.13.2up to date
 async-stream^0.30.3.6up to date
 async-trait^0.10.1.89up to date
 async-walkdir^2.12.1.0up to date
 asyncgit^0.270.27.0up to date
 chrono ⚠️^0.40.4.42maybe insecure
 clap^4.54.5.53up to date
 cli_utils_hoijui^0.100.11.0out of date
 config^0.150.15.19up to date
 const_format^0.20.2.35up to date
 crossbeam-channel^0.50.5.15up to date
 csv-async^1.31.3.1up to date
 fs4^0.130.13.1up to date
 futures^0.30.3.31up to date
 git-version^0.30.3.9up to date
 git2^0.200.20.3up to date
 governor^0.100.10.2up to date
 rand^0.90.9.2up to date
 regex^1.111.12.2up to date
 reqwest^0.120.12.24up to date
 reqwest-middleware^0.40.4.2up to date
 reqwest-retry^0.70.8.0out of date
 serde^1.01.0.228up to date
 serde_json^1.01.0.145up to date
 strum^0.270.27.2up to date
 thiserror^2.02.0.17up to date
 tokio^1.431.48.0up to date
 tracing^0.10.1.43up to date
 tracing-subscriber ⚠️^0.30.3.22maybe insecure
 typed-builder^0.210.23.2out of date
 url^2.52.5.7up to date
 urlencoding^2.12.1.3up to date

Security Vulnerabilities

chrono: Potential segfault in `localtime_r` invocations

RUSTSEC-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

tracing-subscriber: Logging user input may result in poisoning logs with ANSI escape sequences

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