google-research / harness2
Code health
This codebase scores 7.9 out of 10 for code health, which we rate good. It also scores maintainability 7.0 and static performance 8.9 out of 10. The three are scored separately and never blended into one number.
Do next
1 suggested
1 thing worth doing in the week to Oct 14, the last indexed commit, 1 of them now.
Now
- Critical
Clean up what this week's commits left: 20 serious findings in 11 files
1 commit in the last 7 days added or worsened them, and they are still open. Start with
harness2/core/schedule.py, which has 1 critical.- serious findings
- 20
- critical
- 4
- files
- 11
Large 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
- 13.4K
Recent activity
All commitsCommits
Decisions
No decisions extracted yet.
Everything we found
350 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 high severity. Code health251Complex conditional · harness2/core/schedule.py24 findings · 4.5 deducted
- worst item is low severity. Refactoring34main+0.9 health, M effort · third_party/lab_runner/opencode/run_opencode.py
- worst item is medium severity. Doc drift2docs/SETUP.mdDocument names dependencies/codex/home/config.toml, which no longer exists.
- worst item is medium severity. Ownership62harness2/__init__.py100% single-owner concentration, 1 commits in 90d
- worst item is low severity. Dead code1final_messageUnreachable function (21 lines)
Composition
Open the graph- python92%
- shell6%
- dockerfile2%
Explore this codebase
- Docs119 pages across 4 modules
- ChatAsk this codebase a question and get an answer with its sources.
- Files94 files with per-file docs, health and history
- ArchitectureDependency graph, layers, and 8 entry points
- Code healthPer-file scores, 177 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.