/jump to repo

Repos Recent Bookmarks Watched Notes Tags Discover Compare Stats GitHub

Repository brief

google/leveldb

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis

cached 2026-03-31T10:27:51.671Z

1mo ago

google/leveldb

google/leveldb is a widely used, active-but-very-limited-maintenance key-value storage library. It is best suited for forks that need a small, ordered, embedded storage engine rather than a SQL database or client-server system.

Loading tags...

Stars38,933

Forks8,175

Default branchmain

Last pushed2026-03-11T04:06:29Z

Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs

Maintenance:

Magnitude:

Sort:

Selected

Prefer this fork only if you specifically want its internal annotations/custom core tweaks and are prepared to carry maintenance yourself. For most adopters, upstream LevelDB is the safer base because this fork is materially stale and offers no clear product-level expansion.

Choose this fork if you need Bitcoin Core-specific compatibility and are willing to trade upstream freshness for a small set of local maintenance fixes. Choose upstream if you want the newest bug fixes and the broadest community-supported baseline.

Prefer this fork if your goal is understanding or teaching LevelDB internals. Prefer upstream if you need an actively maintained, production-oriented dependency with current bug fixes and compatibility work.

Choose this fork only if Windows-native build/support is the main requirement and you are comfortable inheriting a very old LevelDB base. If you want an actively maintained embedded KV store, upstream or a more current fork is the safer choice.

Choose this fork if you need a lightly modified LevelDB with local fixes around recovery and storage internals. Choose upstream if you want the newest compatibility and bug-fix stream; this fork looks behind and does not show new product expansion.

This looks like a light customization rather than a fundamentally different product.

This fork is materially different enough that adopters should validate long-term maintenance and upgrade cost.

This fork is materially different enough that adopters should validate long-term maintenance and upgrade cost.

Choose this fork only if Bedrock database compatibility is the requirement. If you just want LevelDB itself, upstream is the safer default because this fork is stale and substantially behind.

This looks like a light customization rather than a fundamentally different product.

Fork comparison

messixukejia/leveldb

38/100

stale

moderate

Prefer this fork only if you specifically want its internal annotations/custom core tweaks and are prepared to carry maintenance yourself. For most adopters, upstream LevelDB is the safer base because this fork is materially stale and offers no clear product-level expansion.

Likely purpose

To customize or study LevelDB internals, especially memtable, comparator, encoding, and write-path behavior, with extra comments/tests for understanding or validation.

Best for

Users who want to study or annotate LevelDB internals.; Teams maintaining a private, legacy LevelDB customization with limited appetite for upstream churn.; Projects that value a small, familiar embedded KV store and can own their own maintenance.; Developers experimenting with comparator, coding, or memtable behavior at the storage-engine level.

Additional features

Added internal comments/annotations and test coverage around core storage code.
Tweaked low-level encoding/comparator and memtable-related behavior, which may support custom key ordering or internal experimentation.
Adjusted database/table/cache internals and validation tests, suggesting a fork aimed at internal behavior changes rather than a public API expansion.
Adds performance-oriented execution paths, caching, or faster runtime modes.

Missing features

Misses 158 upstream commits, so it likely lacks many later bug fixes, compiler compatibility updates, and maintenance corrections from upstream.
No evidence of upstream's later C++23/compatibility fixes, deadlock fixes, or dependency bumps.
Appears to lag significantly, which can make newer build environments and edge-case correctness harder to rely on.
It trails upstream by 158 commits, so some recent upstream features and fixes are likely not present yet.

Strengths

Small delta from the original API surface.
Focused changes in core internals rather than broad divergence.
Some added tests suggest an effort to validate behavior.
Could suit teams that want a readable, minimally transformed LevelDB variant.

Risks

Staleness is the main risk: it is far behind upstream maintenance.
Internal changes may be subtle and hard to reason about without strong test coverage.
If adopted for production, the gap to upstream increases the cost of merging fixes.
Likely not a good fit if you need current platform/compiler compatibility or active maintenance.