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 9.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.
Began other-led, now leaning chore.
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 | 1b918944Initial commit | Mnehmos | 7mo ago | +1.8M -0 | 95%Elevated | more lines added than baseline |
| 2 | e13bf568refactor: DRY up code and fix async bug for v1.0 release | Mnehmosclaudeassisted | 7mo ago | +921 -27 | 80%Elevated | more lines added than baseline |
| 3 | 47e34766feat: add lock manager and storage tests | Mnehmos | 7mo ago | +434 -0 | 80%Elevated | more lines added than baseline |
| 4 | c79a9da2docs: improve README with NPM install, badges, correct paths, and all 21 tools | Mnehmos | 7mo ago | +84 -6 | 65%Typical | more lines added than baseline |
| 5 | 3257307cci: add GitHub Actions for CI/CD and NPM publish | Mnehmosclaudeassisted | 7mo ago | +71 -0 | 55%Typical | more lines added than baseline |
| 6 | e515315echore: prepare v1.0 for NPM publication | Mnehmosclaudeassisted | 7mo ago | +233 -1.8M | 45%Typical | more lines added than baseline |
| 7 | 067395f4docs: update PROJECT_KNOWLEDGE.md for v1.0.0 release | Mnehmosclaudeassisted | 7mo ago | +28 -14 | 35%Typical | more lines added than baseline |
| 8 | 343aeedcfix(ci): restore OIDC provenance with NPM_TOKEN fallback | Mnehmos | 7mo ago | +8 -1 | 25%Below typical | fewer lines added than baseline |
| 9 | e03711bcci(publish): use NPM_TOKEN instead of OIDC | Mnehmosclaudeassisted | 7mo ago | +3 -8 | 10%Below typical | fewer lines added than baseline |
| 10 | b2a7373aci(publish): use NPM Trusted Publishing (OIDC) | Mnehmosclaudeassisted | 7mo ago | +3 -2 | 10%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.
Mnehmos/mnehmos.synch.mcp has 10 commits in its history from 1 contributor, the first of them Dec 28, 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.
