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 naga

Dependencies

(21 total, 5 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 arbitrary^1.41.4.2up to date
 arrayvec^0.7.10.7.8up to date
 bit-set^0.80.11.1out of date
 bitflags^2.92.13.1up to date
 cfg-if^11.0.4up to date
 codespan-reporting^0.120.13.1out of date
 half^2.52.7.1up to date
 hashbrown ⚠️^0.150.17.1out of date
 hexf-parse^0.20.2.1up to date
 indexmap^2.72.14.0up to date
 libm^0.2.60.2.16up to date
 log^0.4.210.4.33up to date
 num-traits^0.2.160.2.19up to date
 once_cell^1.211.21.4up to date
 petgraph^0.80.8.3up to date
 pp-rs^0.2.10.2.1up to date
 rustc-hash^1.12.1.3out of date
 serde^1.0.2191.0.229up to date
 spirv^0.30.4.0+sdk-1.4.341.0out of date
 thiserror^2.0.32.0.19up to date
 unicode-ident^1.0.51.0.24up to date

Dev dependencies

(11 total, 7 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 diff^0.10.1.13up to date
 env_logger^0.110.11.11up to date
 hashbrown ⚠️^0.150.17.1out of date
 itertools^0.140.15.0out of date
 ron^0.100.12.2out of date
 rspirv^0.110.13.0+sdk-1.4.341.0out of date
 serde^1.0.2191.0.229up to date
 spirv^0.30.4.0+sdk-1.4.341.0out of date
 strum^0.270.28.0out of date
 toml^0.8.91.1.3+spec-1.1.0out of date
 walkdir^2.32.5.0up to 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.