reijerteunis / seene
Code health
This codebase scores 7.3 out of 10 for code health, which we rate good. It also scores maintainability 7.6 and static performance 9.4 out of 10. The three are scored separately and never blended into one number. Risk is concentrated, as it usually is: 18 of 1,396 files are git hotspots, and they average 6.3 — which is where the fixes pay off most.
Do next
1 thing worth doing in the week to Sep 28, the last indexed commit, 1 of them now.
Now
- Critical
Clean up what this week's commits left: 15 serious findings in 10 files
11 commits in the last 7 days added or worsened them, and they are still open. Start with
harness/report.py, which has 1 critical.- serious findings
- 15
- critical
- 2
- files
- 10
Medium 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
- 20.6K
Recent activity
All commitsCommits
- 9d539fa2SEEN-113: Let a tdd record cite the evidence a return did not invalidate (#29)1d ago
- f04676cddocs(SEEN-111): done3d ago
- cf604d9aSEEN-111: Hold a slice to the context it was routed to, and price it before it is worked (#28)3d ago
- 51054637docs: open SEEN-111 and SEEN-112 (#27)3d ago
- 925e387cdocs(SEEN-106): done3d ago
- 500342dcSEEN-106: Enforce the harness with hooks in both assistants, generated from one source (#26)3d ago
Decisions
- SEEN-086 has no journalproposed · 14h ago
- Receipt hash included in pull request body via APIproposed · 14h ago
- Receipt attests a scoped tree excluding journal-only pathsproposed · 14h ago
- Hash journal records as exact file bytes and link via prev_hashproposed · 14h ago
- Do not count or characterize a ticket's own review rounds in Outcomeproposed · 14h ago
- PR risk/evidence tooling uses a GitHub App that publishes a public per-PR page (not to be installed manually)proposed · 14h ago
Everything we found
437 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 critical severity. Code health243Nested complexity · harness/cli.py41 findings · 7.5 deducted
- worst item is low severity. Refactoring45ask_batch+1.0 health, S effort · harness/jev.py
- worst item is medium severity. Doc drift3docs/harness/workflow.mdDocument names graphify-out/graph.json, which no longer exists.
- worst item is medium severity. Decisions46harness/cli.py28 awaiting review · 18 hotspots ungoverned
- worst item is medium severity. Ownership100harness/gates.py88% single-owner concentration, 11 commits in 90d
Composition
Open the graphExplore this codebase
- Docs291 pages across 5 modules
- ChatAsk this codebase a question and get an answer with its sources.
- Files1,396 files with per-file docs, health and history
- ArchitectureDependency graph, layers, and 27 entry points
- Code healthPer-file scores, 392 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.