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 43% of the 7scored. 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.4 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 feature-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 | fae92e1fAdd initial implementation of occupancy prediction model with database schema and CLI | Hankanman | 1y ago | +1.5K -0 | 93%Elevated | more lines added than baseline |
| 2 | 4c65eb24Refactor AreaOccupancyStorage to utilize ORM for database operations | Hankanman | 1y ago | +554 -417 | 71%Elevated | more lines added than baseline |
| 3 | 8e159ed9Enhance AreaOccupancyStorage with session management and CRUD operations | Hankanman | 1y ago | +612 -331 | 71%Elevated | more lines added than baseline |
| 4 | f42a8bcdRefactor database schema and improve area occupancy management | Hankanman | 1y ago | +297 -344 | 50%Typical | more lines added than baseline |
| 5 | 20722365Implement time prior retrieval and decay handling in occupancy prediction | Hankanman | 1y ago | +132 -20 | 36%Typical | more lines added than baseline |
| 6 | 2e035c69Add combine_priors function and enhance naive_bayes_predict logic | Hankanman | 1y ago | +114 -11 | 21%Below typical | more lines added than baseline |
| 7 | 2c847227Refactor main application to utilize AreaOccupancyStorage for database operations | Hankanman | 1y ago | +34 -20 | 7%Below typical | more 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 7 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.
Hankanman/area_probability has 7 commits in its history from 1 contributor, the first of them Jul 27, 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.
