repowiserepowise
Sign in
burntsushi/ripgrep
OverviewDocsArchitectureKnowledge GraphFilesCode HealthRefactoring

People & History

CommitsContributorsDecisions
ChatPro
Stats
repowiserepowise
ExplorePricingDocs
Sign inIndex repoIndex your repo free
repowiseburntsushi/ripgrep

Commits

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

0of 0 scored

0 commits sit in this repo's top risk tercile, which is 0% of the 0scored. The cut is drawn against this codebase's own history rather than a global curve, so a quiet repo still fills its top band. 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.

Fix commits00%Commits whose subject reads as a bug fix rather than new work.Change diffusion0.00bitsShannon entropy of a commit's churn across its files. Zero is a single file, and every extra bit is a doubling of how widely the change spread.

Review-priority queue

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.

No commits indexed

Per-commit change-risk is captured on the next full index of this repo.

Commit history for burntsushi/ripgrep

Repowise tracks change history across 104 files in burntsushi/ripgrep. In the last 90 days 1 file was touched, 2 times in total, most often dir.rs. Every commit is scored for change risk from its size, spread and the history of the files it touches.