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.
rusthesia(12 total, 6 outdated, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| midir | ^0.5 | 0.9.1 | out of date |
| midly | ^0.4 | 0.5.3 | out of date |
| clap | ^2.32 | 4.5.4 | out of date |
| indoc | ^0.3 | 2.0.5 | out of date |
| font-kit | ^0.5 | 0.13.0 | out of date |
| piano_keyboard | ^0.2 | 0.2.3 | up to date |
| sdl2_timing | ^0.2 | 0.2.0 | up to date |
| chrono ⚠️ | ^0.4 | 0.4.38 | maybe insecure |
| termcolor | ^1.1 | 1.4.1 | up to date |
| thread_local ⚠️ | ^1.0 | 1.1.8 | maybe insecure |
| sdl2 | ^0.33 | 0.36.0 | out of date |
| log | ^0.4 | 0.4.21 | up to date |
chrono: Potential segfault in `localtime_r` invocationsUnix-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.
No workarounds are known.
thread_local: Data race in `Iter` and `IterMut`In the affected version of this crate, {Iter, IterMut}::next used a weaker memory ordering when loading values than what was required, exposing a potential data race
when iterating over a ThreadLocal's values.
Crates using Iter::next, or IterMut::next are affected by this issue.