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 30% of the 10scored. 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.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.
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 | 54ac105aInitial release | Bharat | 1mo ago | +102.8K -0 | 95%Elevated | more lines added than baseline |
| 2 | f405d60eRemove commented-out subtitle lines from various study notes files | Bharat | 1mo ago | +129 -123 | 85%Elevated | more lines added than baseline |
| 3 | 72e74f22Update .gitignore to include llms.txt and add documentation index for LLMs | Bharat | 1mo ago | +81 -1 | 75%Elevated | more lines added than baseline |
| 4 | ed3adaccUpdate documentation links to reflect correct GitHub account | Bharat | 1mo ago | +10 -10 | 65%Typical | more scattered than baseline |
| 5 | 44f1debeRefactor tests to simplify theme assertions and ensure necessary imports | Bharat | 1mo ago | +6 -7 | 55%Typical | fewer lines added than baseline |
| 6 | a5f33904Fix pyproject.toml license config for setuptools PEP 639 | Bharat | 1mo ago | +4 -8 | 45%Typical | fewer lines added than baseline |
| 7 | 19a67334Update site and repo URLs in mkdocs.yml to reflect correct GitHub account | Bharat | 1mo ago | +3 -3 | 35%Typical | fewer lines added than baseline |
| 8 | 11e72fb3Fix fetch-depth configuration in CI workflow for accurate checkout | Bharat | 1mo ago | +2 -0 | 25%Below typical | fewer lines added than baseline |
| 9 | 6156f3a0Remove unused imports in logo.py | Bharat | 1mo ago | +1 -2 | 15%Below typical | fewer lines added than baseline |
| 10 | f82a6597Trigger GitHub Pages deployment | Bharat | 1mo ago | +0 -0 | 5%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 10 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 87 files in bharat940/paperforge. In the last 90 days 87 files were touched, 114 times in total, most often demo_diagrams.py. Every commit is scored for change risk from its size, spread and the history of the files it touches.
