repowise
tran-the-lam/scada-project
tran-the-lam / scada-project
gocppdartmain476bb9d4.4K linessynced 3mo ago
Code health
9.6out of 10Excellent
This codebase scores 9.6 out of 10 for code health, which we rate excellent. It also scores maintainability 9.7 and static performance 9.9 out of 10. The three are scored separately and never blended into one number.
Do next
1 suggested
1 thing worth doing this quarter.
Worth planning
Delete 13 unused symbols and files (82 lines)
Nothing in the graph reaches them, across 6 files; every reader and agent pays to skip them.
- symbols
- 13
- lines
- 82
- 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
- Lines of code
- 4.4K
Recent activity
All commitsCommits
Everything we found
878 open
Every detector's open count by area, each with its worst example. An inventory, not a to-do list: the actions above are the part worth doing.
- worst item is low severity. Code health10Complex method · smart-contract/chaincode/main.go4 findings · 1.5 deducted
- worst item is low severity. Refactoring4cycle[2]: my_application.h->my_application.cc+0.0 health, S effort · application/mydemo/linux/my_application.cc
- worst item is medium severity. Decisions4Let Flutter and plugins handle window messages4 awaiting review
- worst item is medium severity. Ownership842application/mydemo/android/app/src/main/kotlin/com/example/mydemo/MainActivity.kt100% single-owner concentration, not touched in 90 days
- worst item is low severity. Dead code18application/mydemo/android/app/src/main/kotlin/com/example/mydemo/MainActivity.ktUnreachable symbol (10 lines)
Composition
Open the graph- go36%
- cpp26%
- dart23%
- swift11%
- kotlin2%
- Other2%
Explore this codebase
- Docs0 pages across 3 modules
- ChatAsk this codebase a question and get an answer with its sources.
- Files61 files with per-file docs, health and history
- ArchitectureDependency graph, layers, and 8 entry points
- Code healthPer-file scores, 11 open findings, coverage and refactoring targets
- Knowledge graphEntities, communities, and the paths between them
- Change couplingFiles that keep changing together, mined from commit history
- CommitsChange-risk ranked history with agent provenance
- ContributorsBus factor, per-file maintainers, and the human/agent split
- StatsSize class, origin, lifetime churn, rhythm and records
- CostsWhat indexing this snapshot cost, by model and by run.