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
3 commits sit in this repo's top risk tercile, which is 33% of the 9scored. 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 4.3 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.
Consistently other-driven across its history.
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 | e85d35fcinitial commit | Luiz Carlos Melo Muniz | 8mo ago | +620 -0 | 94%Elevated | more lines added than baseline |
| 2 | 0992b531Create Dockerfile | Luiz Carlos Muniz | 7mo ago | +14 -0 | 83%Elevated | more lines added than baseline |
| 3 | 61fad05fUpdate Dockerfile | Luiz Carlos Muniz | 7mo ago | +11 -8 | 72%Elevated | more focused than baseline |
| 4 | b1714cfaUpdate Dockerfile | Luiz Carlos Muniz | 7mo ago | +3 -0 | 61%Typical | fewer lines added than baseline |
| 5 | 387ef74fUpdate MyController.java | Luiz Carlos Muniz | 7mo ago | +2 -1 | 50%Typical | fewer lines added than baseline |
| 6 | 283c36f5Update application.properties | Luiz Carlos Muniz | 7mo ago | +1 -0 | 39%Typical | fewer lines added than baseline |
| 7 | 1107111aUpdate MyController.java | Luiz Carlos Muniz | 7mo ago | +1 -1 | 22%Below typical | fewer lines added than baseline |
| 8 | 9e113194initial commit | Luiz Carlos Melo Muniz | 8mo ago | +1 -1 | 22%Below typical | fewer lines added than baseline |
| 9 | 787c1cd4Update application.properties | Luiz Carlos Muniz | 7mo ago | +0 -1 | 6%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 9 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.
lcmuniz/my-api has 9 commits in its history from 2 contributors, the first of them Dec 13, 2025. 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.
