repowise
laf-us/idaho-vault
LAF-US / IDAHO-VAULT
pythonshellmain827811e940.0K linessynced 1mo ago
Code health
6.8out of 10Fair
Hotspots average 3.3, the place fixes pay off most.
Explore this codebase
- Code health map24hotspots across 37,363 files
- Ownership192sole-owned files: one author, no second reader
- Architecture16modules, 33 entry points
- Decisions26recorded, of which 0 accepted and 26 awaiting review
- Refactoring72open opportunities, one per file
- TestsNo coverage report yet. Run your tests with coverage on, then add the report:
AlsoDocsChatFilesKnowledge graphChange couplingCommitsStatsCosts
Do next · 2
2 things worth doing this quarter.
Worth planning
Update the decision “Submit dependencies from uv.lock instead of GitHub auto-submission”: the code it governs has moved on
Agents and reviewers still follow it, so they are steered by a rule the code no longer keeps.
- status
- Accepted, drifting
Small effort, worth a checkDelete 8 unused symbols and files (250 lines)
Nothing in the graph reaches them, across 5 files; every reader and agent pays to skip them.
- symbols
- 8
- lines
- 250
- safe to delete
- Yes(inferred)
Small effort
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
5 areas
Every detector's open count by area. The actions above are the part worth doing.
- Code health2,719CriticalPrior defects · .ghcp-appmod/skills/java-knowledge-graph/scripts/build_knowledge_graph.py77 findings · 8.0 deducted
- Refactoring72 open opportunitiesMediummain+1.5 health, M effort · simple_ics_audit.py
- Decisions26 to reviewHighSubmit dependencies from uv.lock instead of GitHub auto-submission26 awaiting review, 0 drifting from the code
- Ownership192 sole-owned filesMedium.github/scripts/gh_cli.pyOne author, no second reader
- Dead code12Lowdocument_statesUnreachable function (7 lines)