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 33% 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 7.5 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 | 4682a97cInitial commit | Peter van Liesdonk | 3y ago | +818 -0 | 97thElevated | more lines added than baseline |
| 2 | db182a1finitial tests | Peter van Liesdonk | 3y ago | +156 -3 | 90thElevated | more lines added than baseline |
| 3 | 9b2139e5Options for PEM and URL encoding | Peter van Liesdonk | 3y ago | +97 -32 | 83thElevated | more lines added than baseline |
| 4 | e8809b5cAdded test cases | Peter van Liesdonk | 3y ago | +87 -2 | 77thElevated | more lines added than baseline |
| 5 | 9d0248d6Initial checking | Peter van Liesdonk | 3y ago | +79 -121 | 70thElevated | more lines added than baseline |
| 6 | 35657546Update readme.md | Peter van Liesdonk | 3y ago | +57 -10 | 63thTypical | more lines added than baseline |
| 7 | d7f6330fadded readme | Peter van Liesdonk | 3y ago | +33 -245 | 57thTypical | more lines added than baseline |
| 8 | 6e80acf7Remove newline in non-urlencoded PEM | Peter van Liesdonk | 3y ago | +26 -16 | 50thTypical | more lines added than baseline |
| 9 | 8bea3166Fixes to readme | Peter van Liesdonk | 3y ago | +5 -5 | 43thTypical | fewer lines added than baseline |
| 10 | 4d006448Update readme.md | Peter van Liesdonk | 3y ago | +3 -1 | 37thTypical | fewer lines added than baseline |
| 11 | 9368a0bfUpdate readme.md | Peter van Liesdonk | 3y ago | +2 -2 | 30thBelow typical | fewer lines added than baseline |
| 12 | b26076ffChanged manifest. Fixes #1 | Peter van Liesdonk | 3y ago | +1 -1 | 23thBelow typical | fewer lines added than baseline |
| 13 | 00d3907fDeleted superfluous certs | Peter van Liesdonk | 3y ago | +0 -110 | 17thBelow typical | fewer lines added than baseline |
| 14 | e2527625Fixes to readme | Peter van Liesdonk | 3y ago | +0 -2 | 7thBelow typical | fewer lines added than baseline |
| 15 | 29da7d6bFake test until I found out how to fake a mTLS connection | Peter van Liesdonk | 3y ago | +0 -10 | 7thBelow 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.
pvliesdonk/mtlsforward has 15 commits in its history from 1 contributor, the first of them Dec 14, 2022. No file in the repository changed in the last 90 days. Every commit is scored for change risk from its size, spread and the history of the files it touches.
