repowise
dimitroffvodka/combat-tracker-dock
DimitroffVodka / combat-tracker-dock
javascriptmaster995672b9.5K linessynced 2mo ago
Code health
6.2out of 10Fair
Explore this codebase
- Code health map31files scored
- Ownership13sole-owned files: one author, no second reader
- Architecture2modules, 18 entry points
- Decisions1recorded, of which 0 accepted and 1 awaiting review
- Refactoring8open opportunities, one per file
- TestsNo coverage report yet. Run your tests with coverage on, then add the report:
AlsoDocsChatFilesKnowledge graphChange couplingCommitsStatsCosts
Do next · 0
Nothing stands out in the week to Feb 27, the last indexed commit.
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 health99CriticalFunction hotspot · scripts/systems.js14 findings · 7.5 deducted
- Refactoring8 open opportunitiesMedium<anonymous@2>+1.5 health, S effort · index.js
- Decisions1 to reviewMediumBrowser constraint for version tooltips1 awaiting review, 0 drifting from the code
- Ownership13 sole-owned filesMediummake_post.pyOne author, no second reader