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 wgpu-hal

Dependencies

(41 total, 12 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 android_system_properties^0.1.10.1.5up to date
 arrayvec^0.7.10.7.6up to date
 ash^0.380.38.0+1.3.281up to date
 bit-set^0.80.10.0out of date
 bitflags^2.92.11.1up to date
 block^0.1.60.1.6up to date
 bytemuck^1.221.25.0up to date
 cfg-if^11.0.4up to date
 core-graphics-types^0.20.2.0up to date
 glow^0.160.17.0out of date
 glutin_wgl_sys^0.60.6.1up to date
 gpu-alloc^0.60.6.0up to date
 gpu-allocator^0.270.28.0out of date
 gpu-descriptor^0.3.20.3.2up to date
 hashbrown ⚠️^0.150.17.0out of date
 js-sys^0.3.770.3.95up to date
 khronos-egl^66.0.0up to date
 libc^0.2.1680.2.185up to date
 libloading^0.80.9.0out of date
 log^0.4.210.4.29up to date
 mach-dxcompiler-rs^0.1.40.1.4+2024.11.22-df583a3.1up to date
 metal^0.320.33.0out of date
 naga^26.0.029.0.1out of date
 ndk-sys^0.60.6.0+11769913up to date
 objc^0.2.50.2.7up to date
 ordered-float>=3, <=5.05.3.0out of date
 parking_lot^0.12.30.12.5up to date
 portable-atomic^1.81.13.1up to date
 portable-atomic-util^0.2.40.2.6up to date
 profiling^1.0.11.0.17up to date
 range-alloc^0.10.1.5up to date
 raw-window-handle^0.6.20.6.2up to date
 renderdoc-sys^11.1.0up to date
 rustc-hash^1.12.1.2out of date
 smallvec^1.91.15.1up to date
 thiserror^2.0.32.0.18up to date
 wasm-bindgen^0.2.1000.2.118up to date
 web-sys^0.3.770.3.95up to date
 wgpu-types^26.0.029.0.1out of date
 windows^0.580.62.2out of date
 windows-core^0.580.62.2out of date

Dev dependencies

(7 total, 6 outdated)

CrateRequiredLatestStatus
 env_logger^0.110.11.10up to date
 glam^0.300.32.1out of date
 glutin^0.310.32.3out of date
 glutin-winit^0.40.5.0out of date
 naga^26.0.029.0.1out of date
 raw-window-handle^0.5.20.6.2out of date
 winit^0.290.30.13out of date

Security Vulnerabilities

hashbrown: Borsh serialization of HashMap is non-canonical

RUSTSEC-2024-0402

The borsh serialization of the HashMap did not follow the borsh specification. It potentially produced non-canonical encodings dependent on insertion order. It also did not perform canonicty checks on decoding.

This can result in consensus splits and cause equivalent objects to be considered distinct.

This was patched in 0.15.1.