jaredwray/keyv

Simple key-value storage with support for multiple backends

View on GitHub ↗Jump to charts ↓Open shareable report →

jaredwray/keyv has 3k+ stars and 200+ forks on GitHub, is written in HTML, and was last pushed on Oct 18, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 38 minutes ago
Type:Library / SDKCategory(s):NoSQL, Key-Value & CachesDatabases & Storage
Added to GitGenius on September 21st, 2026
Created on July 7th, 2017
Open Issues & Pull Requests: 1 (+0)
GitHub issues: Enabled
Number of forks: 204
Total Stargazers: 3,201 (+0)
Total Subscribers: 19 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 7.3 hours
Mean response time: 43.6 hours
90th percentile: 4.5 days
Tracked items: 134

Maintainer activity

1 person did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 18, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits. How this is counted.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

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

Recent activity

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

Top labels

  • bug (84)
  • enhancement (34)
  • investigating (24)
  • in progress (14)
  • please vote (3)
  • question (1)
  • storage adapter (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Keyv is a key-value storage abstraction layer that supports multiple backends.

The tool solves the problem of switching between different storage systems by providing a unified interface. Rather than writing code specific to Redis, MongoDB, PostgreSQL, or other backends, developers write once against Keyv's API and can swap storage implementations without changing application code. The abstraction handles the differences between backends transparently, allowing teams to choose the right storage for their deployment without refactoring.

Keyv suits projects that need flexibility in storage choices or may migrate between systems as requirements evolve. It works well for applications using caching, session storage, or other key-value patterns where the underlying backend is an implementation detail. Teams building multi-tenant systems or offering deployment options to customers benefit from the ability to support different storage backends without maintaining separate code paths. The project supports a broad range of backends including Redis, Memcache, MongoDB, MySQL, PostgreSQL, SQLite, and etcd, making it applicable across different infrastructure setups.

The project shows consistent maintenance with regular updates addressing bugs and adding features. Development activity includes ongoing refinement of the core abstraction and its backend implementations. The maintainers respond to issues and pull requests, indicating active stewardship of the codebase. The project maintains documentation and examples that help developers understand how to integrate and configure different backends.