Deps.rs

petroniuss / groupcache

[![dependency status](https://deps.rs/repo/github/petroniuss/groupcache/status.svg)](https://deps.rs/repo/github/petroniuss/groupcache)

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 groupcache

Dependencies

(13 total, all up-to-date)

CrateRequiredLatestStatus
 tonic^0.14.20.14.2up to date
 hashring^0.3.30.3.6up to date
 anyhow^1.01.0.100up to date
 thiserror^2.02.0.17up to date
 axum^0.8.00.8.7up to date
 tokio^1.341.48.0up to date
 serde^1.01.0.228up to date
 rmp-serde^1.11.3.0up to date
 async-trait^0.1.740.1.89up to date
 singleflight-async^0.2.00.2.0up to date
 moka^0.12.10.12.11up to date
 log^0.4.200.4.29up to date
 metrics^0.24.00.24.3up to date

Dev dependencies

(4 total, all up-to-date)

CrateRequiredLatestStatus
 pretty_assertions^1.4.01.4.1up to date
 tokio-stream^0.1.140.1.17up to date
 tokio^1.341.48.0up to date
 rstest^0.26.10.26.1up to date

Crate groupcache-pb

Dependencies

(4 total, all up-to-date)

CrateRequiredLatestStatus
 prost^0.14.10.14.1up to date
 tonic^0.14.20.14.2up to date
 tonic-prost^0.14.20.14.2up to date
 tonic-prost-build^0.14.20.14.2up to date

Build dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 tonic-prost-build^0.14.20.14.2up to date

Crate kubernetes-service-discovery

Dependencies

(14 total, 1 possibly insecure)

CrateRequiredLatestStatus
 tonic^0.14.20.14.2up to date
 axum^0.8.00.8.7up to date
 tower^0.5.10.5.2up to date
 tower-http^0.6.10.6.7up to date
 tokio^1.341.48.0up to date
 serde^11.0.228up to date
 serde_json^11.0.145up to date
 tracing^0.10.1.43up to date
 tracing-subscriber ⚠️^0.30.3.22maybe insecure
 axum-prometheus^0.9.00.9.0up to date
 anyhow^11.0.100up to date
 async-trait^0.10.1.89up to date
 kube^2.0.12.0.1up to date
 k8s-openapi^0.26.00.26.0up to date

Crate simple

Dependencies

(6 total, 1 possibly insecure)

CrateRequiredLatestStatus
 tokio^1.341.48.0up to date
 serde^11.0.228up to date
 tracing^0.10.1.43up to date
 tracing-subscriber ⚠️^0.30.3.22maybe insecure
 anyhow^11.0.100up to date
 async-trait^0.10.1.89up to date

Crate simple-multiple-instances

Dependencies

(8 total, 1 possibly insecure)

CrateRequiredLatestStatus
 tonic^0.14.20.14.2up to date
 tokio^1.341.48.0up to date
 tower-http^0.6.10.6.7up to date
 serde^11.0.228up to date
 tracing^0.10.1.43up to date
 tracing-subscriber ⚠️^0.30.3.22maybe insecure
 anyhow^11.0.100up to date
 async-trait^0.10.1.89up to date

Security Vulnerabilities

tracing-subscriber: Logging user input may result in poisoning logs with ANSI escape sequences

RUSTSEC-2025-0055

Previous versions of tracing-subscriber were vulnerable to ANSI escape sequence injection attacks. Untrusted user input containing ANSI escape sequences could be injected into terminal output when logged, potentially allowing attackers to:

  • Manipulate terminal title bars
  • Clear screens or modify terminal display
  • Potentially mislead users through terminal manipulation

In isolation, impact is minimal, however security issues have been found in terminal emulators that enabled an attacker to use ANSI escape sequences via logs to exploit vulnerabilities in the terminal emulator.

This was patched in PR #3368 to escape ANSI control characters from user input.