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.
azul-layout(52 total, 8 outdated, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| accesskit | ^0.24 | 0.24.1 | up to date |
| agg-rust-azul | ^1.0.3 | 1.0.3 | up to date |
| allsorts-azul | ^0.17.1 | 0.17.1 | up to date |
| azul-core | ^0.0.12 | 0.0.12 | up to date |
| azul-css | ^0.0.12 | 0.0.12 | up to date |
| base64 | ^0.22.1 | 0.23.0 | out of date |
| brotli-decompressor | ^5 | 5.0.3 | up to date |
| chrono ⚠️ | ^0.4 | 0.4.45 | maybe insecure |
| core-foundation | ^0.9 | 0.10.1 | out of date |
| core-graphics | ^0.23 | 0.25.0 | out of date |
| core-text | ^20.1 | 22.0.0 | out of date |
| dirs | ^6.0 | 6.0.0 | up to date |
| fluent | ^0.17 | 0.17.0 | up to date |
| fluent-syntax | ^0.12 | 0.12.0 | up to date |
| gl-context-loader | ^0.1.8 | 0.1.10 | up to date |
| hyphenation | ^0.8.4 | 0.8.4 | up to date |
| icu | ^2.1 | 2.2.0 | up to date |
| icu_provider_blob | ^2.1 | 2.2.0 | up to date |
| image | ^0.25 | 0.25.10 | up to date |
| intl-memoizer | ^0.5 | 0.5.3 | up to date |
| libc | ^0.2 | 0.2.189 | up to date |
| libmimalloc-sys | ^0.1 | 0.1.49 | up to date |
| lru | ^0.16.1 | 0.18.1 | out of date |
| lyon | ^1.0.1 | 1.0.19 | up to date |
| material-icons | ^0.3 | 0.3.0 | up to date |
| objc2 | ^0.6.0 | 0.6.4 | up to date |
| objc2-foundation | ^0.3.0 | 0.3.2 | up to date |
| png | ^0.18 | 0.18.1 | up to date |
| roxmltree | ^0.21.1 | 0.21.1 | up to date |
| rust-fontconfig | >=4.4.7, <4.5 | 4.4.7 | up to date |
| rustls ⚠️ | ^0.23 | 0.23.42 | maybe insecure |
| rustls-rustcrypto | ^0.0.2-alpha | N/A | up to date |
| serde | ^1.0 | 1.0.229 | up to date |
| serde_json | ^1.0 | 1.0.151 | up to date |
| smallvec | ^1.13 | 1.15.2 | up to date |
| strfmt | ^0.2 | 0.2.5 | up to date |
| taffy | ^0.10 | 0.12.2 | out of date |
| tfd | ^0.1 | 0.1.2 | up to date |
| thiserror | ^2.0.17 | 2.0.19 | up to date |
| tikv-jemalloc-sys | ^0.6 | 0.7.1+5.3.1-0-g81034ce1f1373e37dc865038e1bc8eeecf559ce8 | out of date |
| tinyvec | ^1.9.0 | 1.12.0 | up to date |
| unic-langid | ^0.9 | 0.9.6 | up to date |
| unicode-bidi | ^0.3.18 | 0.3.18 | up to date |
| unicode-normalization | ^0.1.24 | 0.1.25 | up to date |
| unicode-segmentation | ^1.12.0 | 1.13.3 | up to date |
| ureq | ^3.3 | 3.3.0 | up to date |
| webpki-roots | ^1.0 | 1.0.9 | up to date |
| writeable | ^0.6 | 0.6.3 | up to date |
| xmlparser | ^0.13.6 | 0.13.6 | up to date |
| xmlwriter | ^0.1.0 | 0.1.0 | up to date |
| zip | ^2.1 | 8.6.0 | out of date |
| zune-jpeg | ^0.5 | 0.5.15 | up to date |
chrono: Potential segfault in `localtime_r` invocationsUnix-like operating systems may segfault due to dereferencing a dangling pointer in specific circumstances. This requires an environment variable to be set in a different thread than the affected functions. This may occur without the user's knowledge, notably in a third-party library.
No workarounds are known.
rustls: rustls network-reachable panic in `Acceptor::accept`A bug introduced in rustls 0.23.13 leads to a panic if the received
TLS ClientHello is fragmented. Only servers that use
rustls::server::Acceptor::accept() are affected.
Servers that use tokio-rustls's LazyConfigAcceptor API are affected.
Servers that use tokio-rustls's TlsAcceptor API are not affected.
Servers that use rustls-ffi's rustls_acceptor_accept API are affected.