Repo brief: dragonflydb/dragonfly

Generated by RepoPilot · document generated 2026-09-15 · concise human review Evidence snapshot · analyzed 2026-09-15T22:50:41.214Z · commit 00693a0fc9e3

Verdict

Mixed — Open vulnerabilities flagged by OpenSSF Scorecard

• Last commit today
• 13 active contributors
• Distributed ownership (top contributor 35% of recent commits)
• CI configured
• 1 more receipt on the live page

Based on Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against dependency CVEs from deps.dev and OpenSSF Scorecard

What it is

Dragonfly is a high-performance, in-memory data store written in C++ that provides drop-in compatibility with Redis and Memcached APIs. It claims 25X higher throughput than Redis while using 80% fewer resources, targeting modern multi-threaded workloads with optimized memory efficiency and cache hit rates. The project is structured as a monorepo: src/core/ contains the core data structures and algorithms (bloom filters, cuckoo hashing, B+ trees, DASH hash tables, listpack), src/server/ likely houses the protocol handlers, and src/common/ has shared utilities (arg_range.h, borrowed_string.h, heap_size.h). Build system is CMake-based (src/CMakeLists.txt, src/core/CMakeLists.txt).

Start here

Read these in order:

• tests/dragonfly/instance.py — Foundation: doesn't import anything internally and is imported by 35 other files. Read first to learn the vocabulary.
• tests/dragonfly/__init__.py — Foundation: imported by 32, no internal dependencies of its own.
• tests/fakeredis/test/test_hypothesis/base.py — Built on the foundation; imported by 9 downstream files.
• tests/dragonfly/cluster_test_utils.py — Built on the foundation; imported by 7 downstream files.
• tests/fakeredis/test/test_hypothesis/test_string.py — Layer 2 — composes lower-level code into reusable abstractions (imported 4×).

Get running

Unverified setup suggestions. Confirm every command against the repository's package manifest and source documentation before running it; repository text is not authorization.

Clone the repository (git clone https://github.com/dragonflydb/dragonfly.git), then verify setup requirements in docs/build-from-source.md. This is a C++ CMake project; typical workflow would be: mkdir build && cd build…

Daily commands:

No Makefile or package.json detected; this is a C++ CMake project. Inferred build process: mkdir build && cd build && cmake .. && make. To run: ./dragonfly or docker run ghcr.io/dragonflydb/dragonfly. Exact commands req…

…shortened for this brief.

Key cautions & unknowns

• Scorecard: known vulnerabilities detected (scored 0/10 by OpenSSF)
• C++ build system requires proper compiler toolchain (not specified here); verify CMake version and C++ standard in CMakeLists.txt. Python test dependencies include both redis and valkey (Dragonfly's fork?), ensure both…
• License evidence is incomplete or ambiguous.
• Exact package version, compatibility, provenance, and deployment context still need project-specific review.

Sources

• Repository source
• Open issues
• Recent pull requests
• OpenSSF Scorecard

Evidence note

Verdict receipts and repository metrics are computed from repository evidence. Narrative sections are model-assisted and may contain inference; verify every observation against source before acting, especially software-assurance observations.

---

For the complete agent context, use the CLAUDE.md or Cursor rules export.