repowiseaws/aws-emulator

aws / aws-emulator

rustmain0c052e911.2M linessynced on Nov 14, 2026

Code health

8.5out of 10Excellent

Hotspots average 5.0, the place fixes pay off most.

Full health report
Documentation12,390pages
0 with model-written prose, 12,390 built from the indexScore validation18/2027.2× baselineTop-ranked files that did go on to need a bug fix

Explore this codebase

AlsoDocsChatFilesKnowledge graphChange couplingCommitsStatsCosts

Do next · 2

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

Worth planning

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

    15 commits in the last 7 days added or worsened long, complex or deeply nested code, still open. Start with services/service-com-amazonaws-cloudformation-cloudformation/src/ops/create_stack.rs (2 findings): tidying it while the change is fresh costs less than after the next one.

    code-shape findings
    22
    files
    18
    commits
    15

  • Review why fixes keep landing in services/service-com-amazonaws-paymentcryptography-paymentcryptographycontrolplane/src/state.rs: tests reach it

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

    commits in 90 days
    5
    bug-fix commits
    4
    line coverage
    Unknown, no report
    tests that reach it
    2 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.