repowisecoleleavitt/unlace

coleleavitt / unlace

rustcmaster463166d485.3K linessynced 1d ago

Code health

5.7out of 10Fair

Hotspots average 3.8, the place fixes pay off most.

Full health report
Documentation2,712pages
0 with model-written prose, 2,712 built from the indexScore validation6/204.3× baselineTop-ranked files that did go on to need a bug fix

Explore this codebase

AlsoDocsChatFilesKnowledge graphChange couplingCommitsStatsCosts

Do next · 3

3 things worth doing in the week to Oct 29, the last indexed commit.

Worth planning

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

    3 commits in the last 7 days added or worsened long, complex or deeply nested code, still open. Start with crates/unlace-output/src/c_printer/mod.rs (8 findings): tidying it while the change is fresh costs less than after the next one.

    code-shape findings
    22
    files
    7
    commits
    3

  • Simplify print_c_attempt in crates/unlace-output/src/c_printer/mod.rs: tests reach it, and fixes keep landing

    Changed 29 times in 90 days, and 6 of those commits were bug fixes.

    commits in 90 days
    29
    bug-fix commits
    6
    line coverage
    Unknown, no report
    tests that reach it
    1 test file, call graph(inferred)
    worth a check

  • Simplify build_function_from_insns in crates/unlace-cli/src/pipeline.rs: tests reach it, and fixes keep landing

    Changed 32 times in 90 days, and 4 of those commits were bug fixes.

    commits in 90 days
    32
    bug-fix commits
    4
    line coverage
    Unknown, no report
    tests that reach it
    7 test files, call graph(inferred)
    worth a check

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.