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.
bevy_egui(13 total, 3 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| arboard | ^3.2.0 | 3.4.0 | up to date |
| bevy | ^0.13 | 0.13.2 | up to date |
| console_log | ^1.0.0 | 1.0.0 | up to date |
| crossbeam-channel | ^0.5.8 | 0.5.12 | up to date |
| egui | ^0.26 | 0.27.2 | out of date |
| js-sys | ^0.3.63 | 0.3.69 | up to date |
| log | ^0.4 | 0.4.21 | up to date |
| thread_local ⚠️ | ^1.1.0 | 1.1.8 | maybe insecure |
| wasm-bindgen | ^0.2.84 | 0.2.92 | up to date |
| wasm-bindgen-futures | ^0.4.36 | 0.4.42 | up to date |
| web-sys | ^0.3.63 | 0.3.69 | up to date |
| webbrowser | ^0.8.2 | 1.0.1 | out of date |
| winit | ^0.29 | 0.30.0 | out of date |
(2 total, all up-to-date)
| Crate | Required | Latest | Status |
|---|---|---|---|
| bevy | ^0.13 | 0.13.2 | up to date |
| version-sync | ^0.9.4 | 0.9.5 | 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.