repowiserepowise
Sign in
baneeishaque/Brute_Force_Attack
OverviewDocsArchitectureKnowledge GraphFilesCode HealthRefactoring

People & History

CommitsContributorsDecisions
ChatPro
Stats
repowiserepowise
ExplorePricingDocs
Sign inIndex repoIndex your repo free
repowisebaneeishaque/Brute_Force_Attack

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

2of 6 scored

2 commits sit in this repo's top risk tercile, which is 33% of the 6scored. 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 8.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.

Fix commits00%Commits whose subject reads as a bug fix rather than new work.Change diffusion0.36bitsShannon 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 threshold8.0out of 10Score a commit has to clear to land in this repo's top tercile.

How the work changed shape

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.

Other100%

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.

Commit review-priority queue
#CommitAuthorWhenLinesRiskTop driver
1
96244a7bIn
Banee Ishaque K
8y ago+1.7K -0
92%Elevated
more lines added than baseline
2
aa69889dl
Banee Ishaque K
7y ago+122 -54
75%Elevated
more lines added than baseline
3
6de485b7Combinations
Banee Ishaque K
8y ago+32 -0
58%Typical
more lines added than baseline
4
f3bfbd2bIn2
Banee Ishaque K
8y ago+19 -19
42%Typical
more lines added than baseline
5
ee01bc1bStrings
Banee Ishaque K
8y ago+8 -5
25%Below typical
fewer lines added than baseline
6
56f4a369All
Banee Ishaque K
8y ago+8 -1
8%Below typical
fewer lines added than baseline
  • 96244a7bIn
    Author
    Banee Ishaque K
    When
    8y ago
    Lines
    +1.7K -0
    Risk
    92%Elevated
  • aa69889dl
    Author
    Banee Ishaque K
    When
    7y ago
    Lines
    +122 -54
    Risk
    75%Elevated
  • 6de485b7Combinations
    Author
    Banee Ishaque K
    When
    8y ago
    Lines
    +32 -0
    Risk
    58%Typical
  • f3bfbd2bIn2
    Author
    Banee Ishaque K
    When
    8y ago
    Lines
    +19 -19
    Risk
    42%Typical
  • ee01bc1bStrings
    Author
    Banee Ishaque K
    When
    8y ago
    Lines
    +8 -5
    Risk
    25%Below typical
  • 56f4a369All
    Author
    Banee Ishaque K
    When
    8y ago
    Lines
    +8 -1
    Risk
    8%Below typical
Showing 6 of 6 commits

How the score behaves here

Change risk →

Two views of the same model: where the cuts fall, and what commit shape lands you above them.

Score distribution

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.

02typical ↑↑ elevated0.05.010.0Change-risk score →
Below typical
Typical
Elevated

Size against diffusion

The 6 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.

1101001,000Lines changed (log) →0.01.3Diffusion →
Below typical2
Typical2
Elevated2

Commit history for baneeishaque/Brute_Force_Attack

baneeishaque/Brute_Force_Attack has 6 commits in its history from 1 contributor, the first of them Sep 19, 2018. 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.