joeferner/redis-commander

Redis management tool written in node.js

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 20 minutes ago
Added to GitGenius on September 17th, 2026
Created on June 18th, 2012
Open Issues & Pull Requests: 75 (+0)
GitHub issues: Enabled
Number of forks: 504
Total Stargazers: 4,001 (+0)
Total Subscribers: 65 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 26.7 hours
Mean response time: 22.3 days
90th percentile: 102.1 days
Tracked items: 24

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 16
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 616 days
Stale 30+ days: 16
Stale 90+ days: 16

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • enhancement (3)
  • help-wanted (2)
  • master fixed (2)
  • bug (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Redis Commander is a web-based management tool for Redis written in Node.js.

The tool solves the problem of inspecting and editing Redis data through a graphical interface rather than command-line tools. It connects to Redis instances—whether standalone servers, Sentinel-based setups, or Redis Cluster deployments—and provides a web UI for viewing and manipulating multiple data types including strings, lists, sets, sorted sets, streams, and ReJSON documents. Users can add, update, and delete data directly through the browser interface.

Redis Commander suits developers and operators who prefer visual data management over CLI interaction and need to work with multiple Redis instances. It works well in environments where a web interface is more practical than terminal access, and it supports complex Redis topologies beyond simple standalone servers. The tool can be deployed via npm installation or as a Docker container, with multi-architecture images available.

The maintainers respond to issues and pull requests within a few days. Work in the issue tracker centers on enhancements, bug fixes labeled as master fixed, and items marked help-wanted, indicating active maintenance focused on feature development and community contributions.