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.
unleash-edge(44 total, 15 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| actix-cors | ^0.7.0 | 0.7.1 | up to date |
| actix-http | ^3.8.0 | 3.10.0 | up to date |
| actix-middleware-etag | ^0.4.1 | 0.4.4 | up to date |
| actix-service | ^2.0.2 | 2.0.3 | up to date |
| actix-web | ^4.8.0 | 4.10.2 | up to date |
| ahash | ^0.8.11 | 0.8.11 | up to date |
| anyhow | ^1.0.86 | 1.0.97 | up to date |
| async-trait | ^0.1.81 | 0.1.88 | up to date |
| chrono | ^0.4.38 | 0.4.40 | up to date |
| cidr | ^0.2.3 | 0.3.1 | out of date |
| clap | ^4.5.9 | 4.5.32 | up to date |
| clap-markdown | ^0.1.4 | 0.1.4 | up to date |
| dashmap | ^6.0.1 | 6.1.0 | up to date |
| futures | ^0.3.30 | 0.3.31 | up to date |
| futures-core | ^0.3.30 | 0.3.31 | up to date |
| iter_tools | ^0.19.0 | 0.24.0 | out of date |
| itertools | ^0.13.0 | 0.14.0 | out of date |
| lazy_static | ^1.4.0 | 1.5.0 | up to date |
| num_cpus | ^1.16.0 | 1.16.0 | up to date |
| opentelemetry | ^0.23.0 | 0.28.0 | out of date |
| opentelemetry-prometheus | ^0.16.0 | 0.28.0 | out of date |
| opentelemetry-semantic-conventions | ^0.15.0 | 0.28.0 | out of date |
| opentelemetry_sdk | ^0.23.0 | 0.28.0 | out of date |
| prometheus | ^0.13.4 | 0.13.4 | up to date |
| prometheus-static-metric | ^0.5.1 | 0.5.1 | up to date |
| rand | ^0.8.5 | 0.9.0 | out of date |
| redis | ^0.25.4 | 0.29.1 | out of date |
| reqwest | ^0.12.5 | 0.12.14 | up to date |
| rustls ⚠️ | ^0.23.11 | 0.23.25 | maybe insecure |
| rustls-pemfile | ^2.1.2 | 2.2.0 | up to date |
| rustls-pki-types | ^1.7.0 | 1.11.0 | up to date |
| semver | ^1.0.23 | 1.0.26 | up to date |
| serde | ^1.0.204 | 1.0.219 | up to date |
| serde_json | ^1.0.120 | 1.0.140 | up to date |
| serde_qs | ^0.13.0 | 0.14.0 | out of date |
| shadow-rs | ^0.30.0 | 1.0.1 | out of date |
| tokio | ^1.38.0 | 1.44.1 | up to date |
| tracing | ^0.1.40 | 0.1.41 | up to date |
| tracing-subscriber | ^0.3.18 | 0.3.19 | up to date |
| ulid | ^1.1.2 | 1.2.1 | up to date |
| unleash-types | ^0.13 | 0.15.10 | out of date |
| unleash-yggdrasil | ^0.13.0 | 0.17.3 | out of date |
| utoipa | ^4.2.3 | 5.3.1 | out of date |
| utoipa-swagger-ui | ^7.1.0 | 9.0.0 | out of date |
(10 total, 3 outdated)
| Crate | Required | Latest | Status |
|---|---|---|---|
| actix-http | ^3.8.0 | 3.10.0 | up to date |
| actix-http-test | ^3.2.0 | 3.2.0 | up to date |
| actix-service | ^2.0.2 | 2.0.3 | up to date |
| env_logger | ^0.11.3 | 0.11.7 | up to date |
| maplit | ^1.0.2 | 1.0.2 | up to date |
| rand | ^0.8.5 | 0.9.0 | out of date |
| test-case | ^3.3.1 | 3.3.1 | up to date |
| testcontainers | ^0.20.0 | 0.23.3 | out of date |
| testcontainers-modules | ^0.8.0 | 0.11.6 | out of date |
| tracing-test | ^0.2.5 | 0.2.5 | up to date |
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.