stackexchange/stackexchange.redis

The Redis client for .NET

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 10 minutes ago
Added to GitGenius on September 10th, 2026
Created on March 14th, 2014
Open Issues & Pull Requests: 217 (+1)
GitHub issues: Enabled
Number of forks: 1,557
Total Stargazers: 6,198 (+0)
Total Subscribers: 308 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 8.9 hours
Mean response time: 60.4 days
90th percentile: 82.6 days
Tracked items: 262

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 88% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Only 6% of issues opened in the past year have been closed. Three people close 79% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 74
New in 7 days: 1
Closed in 7 days: 3
Avg open age: 879 days
Stale 30+ days: 65
Stale 90+ days: 62

Recent activity

Opened in 7 days: 1
Closed in 7 days: 3
Comments in 7 days: 3
Events in 7 days: 8

Top labels

  • ⚙️ area:API (12)
  • ➕ enhancement (12)
  • ⏱️ timeout (9)
  • ❔ question (8)
  • 🪲 bug (8)
  • ⚙️ area:connection (7)
  • 💬 needs-info (5)
  • 🙌 up-for-grabs (5)

Detailed Description

StackExchange.Redis is a .NET client library for communicating with Redis and Redis-compatible servers.

The tool solves the problem of connecting .NET applications to Redis and RESP-compatible servers by providing a managed client that handles the protocol communication. It works by abstracting the RESP protocol details, allowing developers to interact with Redis servers through a .NET API rather than managing raw socket connections or protocol formatting themselves.

Developers should choose this library if they are building .NET applications that need to integrate with Redis, Azure Managed Redis, Garnet, Valkey, AWS ElastiCache, or other Redis-like servers. The tool is designed to work with any server that implements a Redis-like API, making it suitable for projects using various Redis-compatible backends across different cloud providers and self-hosted deployments.

The project maintains an active release cycle with documented release notes, and the maintainers respond to compatibility issues by accepting reports when servers claiming Redis compatibility encounter problems with the client.