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
6 commits sit in this repo's top risk tercile, which is 40% of the 15scored. 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.1 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 | Risk | Top driver |
|---|---|---|---|---|---|---|
| 1 | e95e8ef9complexity and cost based routing added | athtripathi | 2mo ago | +1.3K -85 | 93%Elevated | more lines added than baseline |
| 2 | 091d1841added model vault, ran migrations | athtripathi | 2mo ago | +1.6K -15 | 93%Elevated | more lines added than baseline |
| 3 | dfc88474added fallback engine | athtripathi | 2mo ago | +710 -532 | 83%Elevated | more lines added than baseline |
| 4 | eeaa5dccredis warm up done and redis cache working | athtripathi | 2mo ago | +533 -56 | 77%Elevated | more lines added than baseline |
| 5 | 8d4ab3cdreadme added | athtripathi | 2mo ago | +591 -3 | 67%Elevated | more lines added than baseline |
| 6 | 7d3253ccmessage chat completion done | athtripathi | 2mo ago | +405 -1 | 67%Elevated | more lines added than baseline |
| 7 | 8247445fadded gitignore | athtripathi | 2mo ago | +216 -0 | 57%Typical | more lines added than baseline |
| 8 | 29ff1922circuit breaker added | athtripathi | 2mo ago | +248 -5 | 50%Typical | more lines added than baseline |
| 9 | 0b1de111setup basic | athtripathi | 2mo ago | +218 -0 | 43%Typical | more lines added than baseline |
| 10 | 0e11de00docker added | athtripathi | 2mo ago | +123 -0 | 37%Typical | more lines added than baseline |
| 11 | d1dbf305docker section added in readme | athtripathi | 2mo ago | +100 -0 | 27%Below typical | more lines added than baseline |
| 12 | f179b64bstreaming responses added | athtripathi | 2mo ago | +115 -7 | 27%Below typical | more lines added than baseline |
| 13 | 28f88f5fadded images | athtripathi | 2mo ago | +41 -0 | 17%Below typical | more lines added than baseline |
| 14 | 177f3141improved readme | athtripathi | 2mo ago | +2 -2 | 10%Below typical | fewer lines added than baseline |
| 15 | 6ff14294updated readme | athtripathi | 2mo ago | +0 -3 | 3%Below typical | fewer 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 15 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.
Repowise tracks change history across 52 files in ath34-tech/routellmesh. In the last 90 days 52 files were touched, 80 times in total, most often service.py. Every commit is scored for change risk from its size, spread and the history of the files it touches.
