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
8 commits sit in this repo's top risk tercile, which is 35% of the 23scored. 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.0 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 feature-led, now leaning fix.
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 | 31ca35c8feat(dashboard): implement full React dashboard with all features | vaibhav | 4mo ago | +6.5K -4 | 98%Elevated | more lines added than baseline |
| 2 | d3a79b95feat: initial project setup and infrastructure boilerplate | vaibhav | 5mo ago | +3.4K -0 | 93%Elevated | more lines added than baseline |
| 3 | ca9bda45feat(auth, webhooks, events): implement core API layer | vaibhav | 5mo ago | +661 -0 | 89%Elevated | more lines added than baseline |
| 4 | 9df66679Revise README for improved clarity and organization | Vaibhav Bhardwaj | 4mo ago | +571 -264 | 85%Elevated | more lines added than baseline |
| 5 | 95b879a5feat(delivery-engine): implement BullMQ queue, delivery worker, and HMAC signing | vaibhav | 4mo ago | +470 -68 | 80%Elevated | more lines added than baseline |
| 6 | af718cd9Revise README for improved clarity and detail | Vaibhav Bhardwaj | 4mo ago | +392 -2 | 74%Elevated | more lines added than baseline |
| 7 | 37a8a4c6feat(analytics, rate-limiting, idempotency): implement observability and protection layer | vaibhav | 4mo ago | +400 -5 | 74%Elevated | more lines added than baseline |
| 8 | ea8a20fcfeat(dlq, tracking): implement DLQ endpoints and delivery history | vaibhav | 4mo ago | +305 -8 | 67%Elevated | more lines added than baseline |
| 9 | 3990c5a7feat(deployment): add production Docker setup, Nginx, and GitHub Actions CI/CD | vaibhav | 4mo ago | +300 -12 | 63%Typical | more lines added than baseline |
| 10 | 6b40bb30Initial commit | Vaibhav Bhardwaj | 5mo ago | +162 -0 | 59%Typical | more lines added than baseline |
| 11 | aa04f2e8minor fixes to the code | vaibhav | 4mo ago | +32 -32 | 54%Typical | more lines added than baseline |
| 12 | 2d5e3cb4feat: add demo login for recruiters | vaibhav | 4mo ago | +19 -0 | 50%Typical | more lines added than baseline |
| 13 | a0ba94ccfix: proxy API through vercel to fix mixed content | vaibhav | 4mo ago | +10 -5 | 46%Typical | more scattered than baseline |
| 14 | 8dc472ffdashboard deployed to vercel and specifics added in src/server.ts | vaibhav | 4mo ago | +6 -1 | 41%Typical | fewer lines added than baseline |
| 15 | a88c931efix: fix Redis connection for production Docker environment and add OpenSSL to Dockerfile | vaibhav | 4mo ago | +5 -5 | 37%Typical | fewer lines added than baseline |
| 16 | 910640e8fix(dashboard): hardcode production API URL for Vercel deployment | vaibhav | 4mo ago | +3 -3 | 33%Below typical | fewer lines added than baseline |
| 17 | a9e1ed9afix: fix GitHub Actions workflow YAML syntax | vaibhav | 4mo ago | +2 -40 | 28%Below typical | fewer lines added than baseline |
| 18 | e26d050aUpdate architecture section in README | Vaibhav Bhardwaj | 4mo ago | +1 -34 | 24%Below typical | fewer lines added than baseline |
| 19 | 39b9c776fix: use relative API path in api.ts to fix mixed content | vaibhav | 4mo ago | +1 -1 | 15%Below typical | fewer lines added than baseline |
| 20 | 1d794240connecting backend and frontend | vaibhav | 4mo ago | +1 -1 | 15%Below typical | fewer lines added than baseline |
| 21 | 4e41e6feci: test GitHub Actions deployment pipeline | vaibhav | 4mo ago | +1 -0 | 15%Below typical | fewer lines added than baseline |
| 22 | 976d6ab2ci: retrigger deployment | vaibhav | 4mo ago | +0 -0 | 4%Below typical | fewer lines added than baseline |
| 23 | e36caa52ci: trigger GitHub Actions deployment | vaibhav | 4mo ago | +0 -0 | 4%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 23 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 49 files in vaibhavxbhardwaj/webhook-delivery-engine. 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.
