repowiserepowise
Sign in
baneeishaque/Scrap_Soundcloud_Sieve
OverviewDocsArchitectureKnowledge GraphFilesCode HealthRefactoring

People & History

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

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 7 scored

2 commits sit in this repo's top risk tercile, which is 29% of the 7scored. 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 3.9 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.52bitsShannon 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 threshold3.9out 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.

Began other-led, now leaning feature.

Feature43%
Deps14%
Other43%

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
de6da41bInitial commit
Banee Ishaque K
7y ago+1.2K -0
93%Elevated
more lines added than baseline
2
b825895arequirements.txt
Banee Ishaque K
6y ago+9 -2
79%Elevated
more scattered than baseline
3
e135371aAdd .whitesource configuration file
whitesource-bolt-for-github[bot]
7y ago+8 -0
64%Typical
fewer lines added than baseline
4
504d7a8cUpdate .pyup.yml
Banee Ishaque K
5y ago+8 -1
50%Typical
fewer lines added than baseline
5
8f89228aAdd renovate.json
Renovate Bot
4y ago+5 -0
29%Below typical
fewer lines added than baseline
6
02d87359create pyup.io config file
pyup-bot
5y ago+5 -0
29%Below typical
fewer lines added than baseline
7
d9cda3bcUpdate .whitesource
Banee Ishaque K
5y ago+2 -2
7%Below typical
fewer lines added than baseline
  • de6da41bInitial commit
    Author
    Banee Ishaque K
    When
    7y ago
    Lines
    +1.2K -0
    Risk
    93%Elevated
  • b825895arequirements.txt
    Author
    Banee Ishaque K
    When
    6y ago
    Lines
    +9 -2
    Risk
    79%Elevated
  • e135371aAdd .whitesource configuration file
    Author
    whitesource-bolt-for-github[bot]
    When
    7y ago
    Lines
    +8 -0
    Risk
    64%Typical
  • 504d7a8cUpdate .pyup.yml
    Author
    Banee Ishaque K
    When
    5y ago
    Lines
    +8 -1
    Risk
    50%Typical
  • 8f89228aAdd renovate.json
    Author
    Renovate Bot
    When
    4y ago
    Lines
    +5 -0
    Risk
    29%Below typical
  • 02d87359create pyup.io config file
    Author
    pyup-bot
    When
    5y ago
    Lines
    +5 -0
    Risk
    29%Below typical
  • d9cda3bcUpdate .whitesource
    Author
    Banee Ishaque K
    When
    5y ago
    Lines
    +2 -2
    Risk
    7%Below typical
Showing 7 of 7 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.

03typical ↑elevated ↑0.05.010.0Change-risk score →
Below typical
Typical
Elevated

Size against diffusion

The 7 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.02.0Diffusion →
Below typical3
Typical2
Elevated2

Commit history for baneeishaque/Scrap_Soundcloud_Sieve

baneeishaque/Scrap_Soundcloud_Sieve has 10 commits in its history from 4 contributors, the first of them Jul 29, 2019. 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.