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.
amethyst(31 total, 7 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| amethyst_animation | ^0.15.3 | 0.15.3 | up to date |
| amethyst_assets | ^0.15.3 | 0.15.3 | up to date |
| amethyst_audio | ^0.15.3 | 0.15.3 | up to date |
| amethyst_config | ^0.15.3 | 0.15.3 | up to date |
| amethyst_controls | ^0.15.3 | 0.15.3 | up to date |
| amethyst_core | ^0.15.3 | 0.15.3 | up to date |
| amethyst_derive | ^0.15.3 | 0.15.3 | up to date |
| amethyst_error | ^0.15.3 | 0.15.3 | up to date |
| amethyst_gltf | ^0.15.3 | 0.15.3 | up to date |
| amethyst_input | ^0.15.3 | 0.15.3 | up to date |
| amethyst_locale | ^0.15.3 | 0.15.3 | up to date |
| amethyst_network | ^0.15.3 | 0.15.3 | up to date |
| amethyst_rendy | ^0.15.3 | 0.15.3 | up to date |
| amethyst_tiles | ^0.15.3 | 0.15.3 | up to date |
| amethyst_ui | ^0.15.3 | 0.15.3 | up to date |
| amethyst_utils | ^0.15.3 | 0.15.3 | up to date |
| amethyst_window | ^0.15.3 | 0.15.3 | up to date |
| crossbeam-channel | ^0.4.2 | 0.5.13 | out of date |
| derivative | ^2.1.1 | 2.2.0 | up to date |
| failure | ^0.1.7 | 0.1.8 | up to date |
| fern | ^0.6.0 | 0.7.0 | out of date |
| glsl-layout ⚠️ | ^0.3.2 | 0.5.0 | out of date |
| lazy_static | ^1.4.0 | 1.5.0 | up to date |
| log | ^0.4.8 | 0.4.22 | up to date |
| palette | ^0.4 | 0.7.6 | out of date |
| rayon | ^1.3.0 | 1.10.0 | up to date |
| rustc_version_runtime | ^0.2.0 | 0.3.0 | out of date |
| sentry | ^0.18.0 | 0.34.0 | out of date |
| serde | ^1.0.104 | 1.0.215 | up to date |
| thread_profiler | ^0.3.0 | 0.3.0 | up to date |
| winit | ^0.19 | 0.30.5 | out of date |
glsl-layout: Double drop upon panic in 'fn map_array()'Affected versions of this crate did not guard against panic within the user-provided function f (2nd parameter of fn map_array), and thus panic within f
causes double drop of a single object.
The flaw was corrected in the 0.4.0 release by wrapping the object vulnerable
to a double drop within ManuallyDrop<T>.