repowiseyetone/magpie

yetone / magpie

gojavascriptmain1e285771.3M linessynced on Nov 12, 2026

Code health

6.4out of 10Fair

Hotspots average 1.8, the place fixes pay off most.

Full health report
Documentation3,271pages
46 with model-written prose, 3,225 built from the indexScore validation4/2046.4× baselineTop-ranked files that did go on to need a bug fix

Explore this codebase

AlsoDocsChatFilesKnowledge graphChange couplingCommitsStatsCosts

Do next · 1

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

Worth planning

  • Tidy the code shape this week's commits left: 17 findings in 10 files

    11 commits in the last 7 days added or worsened long, complex or deeply nested code, still open. Start with internal/gui/assets/plugins/routing/client.js (4 findings): tidying it while the change is fresh costs less than after the next one.

    code-shape findings
    17
    files
    10
    commits
    11

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

5 areas

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