sanic-org / sanic
pythonmain5ffc7b335.6K linessynced on May 31, 2026
Code health
7.2out of 10Good
Hotspots average 5.0, the place fixes pay off most.
Explore this codebase
- Code health map10hotspots across 470 files
- Ownership164sole-owned files: one author, no second reader
- Architecture8modules, 11 entry points
- Decisions79recorded, of which 0 in force and 79 background
- RefactoringNo refactoring analysis yet
- TestsNo coverage report yet. Run your tests with coverage on, then add the report:
AlsoDocsChatFilesKnowledge graphChange couplingCommitsStatsCosts
Do next · 2
2 things worth doing in the week to May 31, the last indexed commit.
Worth planning
Address the finding in register
sanic/blueprints.py:333
register has a bumpy road finding; function changed in 35 commits.
- gain
- up to under +0.1 health on this file(inferred)
- finding
- Bumpy road
- size
- CCN 26, 150 lines, nests 3 deep
- severity
- high
Medium effort, worth a checkAddress the finding in url_for
sanic/app.py:942
url_for has a bumpy road finding; function changed in 22 commits.
- gain
- up to under +0.1 health on this file(inferred)
- finding
- Bumpy road
- size
- CCN 39, 158 lines, nests 4 deep
- severity
- high
Medium effort, 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
Small effort
Everything we found
4 areas
Every detector's open count by area. The actions above are the part worth doing.
- Code health493 open findingsCriticalFunction hotspot · sanic/app.py48 findings · 7.5 deducted
- Decisions0 drifting from the codeMediumtests/test_http.pyHigh-churn file with no governing decision
- Ownership164 sole-owned filesMediumsanic/__version__.pyOne author, no second reader
- Dead code104Lowexamples/exception_monitoring.pyUnreachable symbol (30 lines)