natebjones-projects / ob1
Code health
This codebase scores 7.4 out of 10 for code health, which we rate good. It also scores maintainability 7.9 and static performance 9.5 out of 10. The three are scored separately and never blended into one number. Risk is concentrated, as it usually is: 14 of 791 files are git hotspots, and they average 4.9 — which is where the fixes pay off most.
Do next
2 things worth doing this quarter.
Worth planning
Update the decision “Use append-only audit table with author_session_id to track operational changes”: 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 41 unused symbols and files (766 lines)
Nothing in the graph reaches them, across 20 files; every reader and agent pays to skip them.
- symbols
- 41
- lines
- 766
- safe to delete
- Yes(inferred)
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
- 98.0K
Recent activity
All commitsCommits
- 8505c0c3docs: add community credit to rest-api README3mo ago
- 3ce7fcf1docs: add community contribution credit3mo ago
- 2af92f6bdocs: align chrome capture README with contribution conventions3mo ago
- 83afa002[integrations] enhanced-mcp: note single-tenant key + CORS rationale3mo ago
- 13c23742[integrations] rest-api: document single-tenant trust model3mo ago
- 57856c05[integrations] rest-api: header-only auth, drop ?key= query param3mo ago
Decisions
- Use append-only audit table with author_session_id to track operational changesactive · 1mo ago
- [recipes] Replace local MCP pattern with custom connectorsproposed · 1mo ago
- [schemas][recipes] Provenance chains (derivation tracking) + security restrictionproposed · 1mo ago
- [recipes] Gmail import: direct Supabase insert + fingerprint dedupproposed · 1mo ago
- [recipes] ChatGPT import with LLM summarizationproposed · 1mo ago
- [recipes] ChatGPT import v2: multi-thought knowledge extractionproposed · 1mo ago
Everything we found
1,517 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 health945Nested complexity · integrations/chrome-capture-extension/background/service-worker.js23 findings · 7.5 deducted
- worst item is medium severity. Refactoring196<anonymous>+1.5 health, S effort · integrations/chrome-capture-extension/lib/gemini-sync-state.js
- worst item is high severity. Decisions33Use append-only audit table with author_session_id to track operational changes1 drifting from the code · 18 awaiting review · 14 hotspots ungoverned
- worst item is medium severity. Ownership286integrations/enhanced-mcp/index.ts100% single-owner concentration, 9 commits in 90d
- worst item is low severity. Dead code57checkHealthUnreachable function (4 lines)
Composition
Open the graphExplore this codebase
- Docs432 pages across 9 modules
- ChatAsk this codebase a question and get an answer with its sources.
- Files791 files with per-file docs, health and history
- ArchitectureDependency graph, layers, and 70 entry points
- Code healthPer-file scores, 950 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.