repowiseducktors/turborepo-remote-cache

ducktors / turborepo-remote-cache

typescriptmain9efa1c67.5K linessynced 1h ago

Code health

8.4out of 10Good

Hotspots average 7.5, the place fixes pay off most.

Full health report
Documentation47pages
10 with model-written prose, 37 built from the indexScore validation10/202.9× baselineTop-ranked files that did go on to need a bug fix

Explore this codebase

AlsoDocsChatFilesKnowledge graphChange couplingCommitsStatsCosts

Do next · 1

1 thing worth doing in the week to Oct 30, the last indexed commit.

Worth planning

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

    1 commit in the last 7 days added or worsened long, complex or deeply nested code, still open. Start with src/plugins/remote-cache/routes/put-artifact.ts (1 finding): tidying it while the change is fresh costs less than after the next one.

    code-shape findings
    2
    files
    2
    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

4 areas

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