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
5 commits sit in this repo's top risk tercile, which is 36% of the 14scored. 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 6.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 | Risk | Top driver |
|---|---|---|---|---|---|---|
| 1 | a2cf78eeInitial deploy | Durvesh Thorat | 2mo ago | +631 -0 | 96%Elevated | more lines added than baseline |
| 2 | f6aab89bUpdated ReadME | Durvesh Thorat | 2mo ago | +143 -8 | 89%Elevated | more lines added than baseline |
| 3 | d501f33bFix README encoding | Durvesh Thorat | 2mo ago | +50 -49 | 82%Elevated | more lines added than baseline |
| 4 | 1521213dRemove HF frontmatter for GitHub | Durvesh Thorat | 2mo ago | +47 -49 | 75%Elevated | more lines added than baseline |
| 5 | bf3031fbRemove HF frontmatter for GitHub | Durvesh Thorat | 2mo ago | +45 -46 | 68%Elevated | more lines added than baseline |
| 6 | 8858404aAdd README | Durvesh Thorat | 2mo ago | +11 -0 | 61%Typical | more focused than baseline |
| 7 | a2311f8aUpdated ReadME | Durvesh Thorat | 2mo ago | +9 -0 | 54%Typical | fewer lines added than baseline |
| 8 | 71baa4b4fix loss cupy to numpy | Durvesh Thorat | 2mo ago | +2 -2 | 46%Typical | fewer lines added than baseline |
| 9 | f2ac85e5Fix emoji encoding | Durvesh Thorat | 2mo ago | +2 -1 | 39%Typical | fewer lines added than baseline |
| 10 | 9c2dd796confidence updated to percentage | Durvesh Thorat | 2mo ago | +1 -1 | 21%Below typical | fewer lines added than baseline |
| 11 | d4ad11c3Fix encoding | Durvesh Thorat | 2mo ago | +1 -1 | 21%Below typical | fewer lines added than baseline |
| 12 | 5d201aecFix encoding | Durvesh Thorat | 2mo ago | +1 -1 | 21%Below typical | fewer lines added than baseline |
| 13 | 2d27a76cfix activations cupy to numpy | Durvesh Thorat | 2mo ago | +1 -1 | 21%Below typical | fewer lines added than baseline |
| 14 | b8ddd493Remove HF frontmatter for GitHub | Durvesh Thorat | 2mo ago | +0 -9 | 4%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 14 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 8 files in durvesh-thorat/neurocipher. In the last 90 days 8 files were touched, 11 times in total, most often activations.py. Every commit is scored for change risk from its size, spread and the history of the files it touches.
