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.
obvhs(9 total, 1 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| bytemuck | ^1 | 1.25.0 | up to date |
| glam | >=0.30, <0.32 | 0.32.1 | out of date |
| half | ^2 | 2.7.1 | up to date |
| log | ^0.4 | 0.4.29 | up to date |
| profiling | ^1 | 1.0.17 | up to date |
| rayon | ^1 | 1.11.0 | up to date |
| rdst | ^0.20 | 0.20.14 | up to date |
| static_assertions | ^1 | 1.1.0 | up to date |
| thread_local ⚠️ | ^1 | 1.1.9 | maybe insecure |
(6 total, all up-to-date)
| Crate | Required | Latest | Status |
|---|---|---|---|
| argh | ^0.1 | 0.1.19 | up to date |
| image | ^0.25 | 0.25.10 | up to date |
| minifb | ^0.28 | 0.28.0 | up to date |
| obj | ^0.10 | 0.10.2 | up to date |
| rayon | ^1 | 1.11.0 | up to date |
| ruzstd | ^0.8 | 0.8.2 | up to date |
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.