repowiserepowise-dev/repowise-bench

repowise-dev / repowise-bench

pythonmaster0fb3c0355.3K linessynced 3w ago

Code health

7.3out of 10Good

Hotspots average 4.9, the place fixes pay off most.

Full health report
Documentation578pages
0 with model-written prose, 578 built from the indexScore validation8/205.9× baselineTop-ranked files that did go on to need a bug fix

Explore this codebase

AlsoDocsChatFilesKnowledge graphChange couplingCommitsStatsCosts

Do next · 1

3 things worth doing in the week to Oct 1, the last indexed commit, 2 of them now.

Worth planning

  • Tidy the code shape this week's commits left: 4 findings in 3 files

    1 commit in the last 7 days added or worsened long, complex or deeply nested code, still open. Start with graph/experiments/g9-language-oracles/score.py (2 findings): tidying it while the change is fresh costs less than after the next one.

    code-shape findings
    4
    files
    3
    commits
    1

Improve what Repowise can see

  • Add a test coverage report

    Without one, Repowise cannot tell tested code from untested code, so every test-related action says “unknown”.

    line coverage
    Unknown, no report

Everything we found

6 areas

Every detector's open count by area. The actions above are the part worth doing.