Every commit scored for change-risk against this repo's own history, so 'elevated' means elevated here rather than on some global curve.
Needs review
2 commits sit in this repo's top risk tercile, which is 40% of the 5scored. The cut is drawn against this codebase's own history rather than a global curve, so a quiet repo still fills its top band, and here it starts at 9.8 out of 10. What pushes a commit up is size and spread together: a large change confined to one area scores below a smaller one scattered across a dozen files.
Commit categories over time, read off the subject line. Fixes carry the accent because that is the series this chart exists to show.
How this repo's commit mix shifts over time.
Ranked by change-risk, highest first. Priority is a tercile of this repo's own distribution, so a quiet repo still fills its top band.
| # | Commit | Author | When | Lines | Review priority | Top driver |
|---|---|---|---|---|---|---|
| 1 | f70659c2docs: publish comprehensive system architecture and consensus specifications | bharqav | 1mo ago | +2.4K -115 | 80thElevated | more lines added than baseline |
| 2 | ea2b6352Initial commit | bharqav | 2mo ago | +5.3K -0 | 80thElevated | more lines added than baseline |
| 3 | b7258d79refactor(core): modularize architecture into src/dkvs package structure | bharqav | 1mo ago | +2.5K -4.7K | 50thTypical | more lines added than baseline |
| 4 | 4584e0a5test: establish comprehensive unit and integration test suites | bharqav | 1mo ago | +918 -0 | 30thBelow typical | more lines added than baseline |
| 5 | 9ff1654fbuild: configure CI workflows, Makefile tooling, and container packaging | bharqav | 1mo ago | +360 -33 | 10thBelow typical | more lines added than baseline |
Two views of the same model: where the cuts fall, and what commit shape lands you above them.
Every scored commit, binned on the raw 0 to 10 score rather than the percentile. Percentile ranks are uniform by construction, so that axis has no shape to draw. The dashed lines are the tercile cuts behind each row's priority pill.
The 5 most recent commits, on their own recency sample rather than the feed above: that defaults to risk-sorted, so reusing it would plot only the top tercile and call it the spread. Big and scattered is what the model penalises. Click a dot to open it.
bharqav/distributed-kv-store has 5 commits in its history from 1 contributor, the first of them Jun 28, 2026. In the last 90 days 38 files were touched, 43 times in total, most often bench.py. Every commit is scored for change risk from its size, spread and the history of the files it touches.
