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
4 commits sit in this repo's top risk tercile, which is 36% of the 11scored. 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 8.7 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.
Began other-led, now leaning feature.
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 | 915720a1feat: implement item design | Jacob LeCoq | 3mo ago | +1.8K -249 | 91thElevated | more lines added than baseline |
| 2 | 9d27195cinitial project setup | Adam Scott | 9mo ago | +2.3K -0 | 91thElevated | more lines added than baseline |
| 3 | 04b95ab7add testing setup and instructions | Adam Scott | 9mo ago | +1.1K -4 | 77thElevated | more lines added than baseline |
| 4 | 449cb9bafeat: implement functions to determine most frequent and dominant secure tags | Jacob LeCoq | 3mo ago | +191 -0 | 68thElevated | more lines added than baseline |
| 5 | df098eafchore: Add TEST.md with testing instructions | Jacob LeCoq | 3mo ago | +50 -0 | 59thTypical | more lines added than baseline |
| 6 | 71b7e2fbfeat: add support for resolving DynamoDB table names from environment variables | Jacob LeCoq | 3mo ago | +46 -4 | 50thTypical | more lines added than baseline |
| 7 | 20df725fdoc: add glossary | Karina | 9mo ago | +45 -0 | 41thTypical | more lines added than baseline |
| 8 | ffbd74fdadd prereqs | Adam Scott | 9mo ago | +27 -3 | 32thBelow typical | more lines added than baseline |
| 9 | 3aad9ec2add license | Adam Scott | 9mo ago | +22 -1 | 23thBelow typical | more lines added than baseline |
| 10 | f2ef7cb8add link to GETTING_STARTED.md | Adam Scott | 9mo ago | +9 -1 | 14thBelow typical | fewer lines added than baseline |
| 11 | 7b379bdcdoc: readme | Karina | 9mo ago | +5 -1 | 5thBelow 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 11 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 19 files in HexSleeves/item-challenge. In the last 90 days 17 files were touched, 19 times in total, most often dynamodb.test.ts. Every commit is scored for change risk from its size, spread and the history of the files it touches.
