goniszewski / grimoire
Code health
This codebase scores 6.6 out of 10 for code health, which we rate fair. It also scores maintainability 8.4 and static performance 9.8 out of 10. The three are scored separately and never blended into one number. Risk is concentrated, as it usually is: 60 of 542 files are git hotspots, and they average 5.1 — which is where the fixes pay off most.
Do next
1 thing worth doing this quarter.
Worth planning
Delete 54 unused symbols and files (476 lines)
Nothing in the graph reaches them, across 24 files; every reader and agent pays to skip them.
- symbols
- 54
- lines
- 476
- 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 effortReview the 13 proposed decisions
None is accepted yet, so nothing can drift from one and agents get no enforced guidance from them.
- proposed
- 13
- accepted
- 0
Medium effort
- Lines of code
- 105.3K
Recent activity
All commitsCommits
- 53230016release(1.0.1): publish patch release (#204)2mo ago
- 4620135ddocs: remove maintainer-internal content from public-facing docs2mo ago
- 8bbc0f20chore(release): adopt Grimoire 1.0 branding and finalize release metadata2mo ago
- 89d4fbecdocs: add CLAUDE.md contributor and repository guidelines2mo ago
- 93b759eetest(e2e): cover redesigned library controls2mo ago
- 26832c8ffeat(ui): add quiet operational redesign2mo ago
Decisions
- Use real 1.0.1 artifact SHAs for release archives and Homebrew baselinesproposed · 1mo ago
- Derive outgoing User-Agent from packaged versionproposed · 1mo ago
- Bump 1.0.1 version identity across manifests and contractsproposed · 1mo ago
- Rebuild sqlite-vec index atomically at bootproposed · 1mo ago
- Align e2e mocks/specs with real daemon version and repo URLsproposed · 1mo ago
- Derive fetcher User-Agent from Grimoire versionproposed · 1mo ago
Everything we found
1,015 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 health554Untested hotspot · daemon/src/settings.ts20 findings · 9.5 deducted
- worst item is medium severity. Refactoring41nextCronRunAt+1.5 health, S effort · daemon/src/lib/cron.ts
- worst item is medium severity. Decisions73src/pages/Settings.tsx13 awaiting review · 60 hotspots ungoverned
- worst item is medium severity. Ownership293src/lib/api.ts100% single-owner concentration, 41 commits in 90d
- worst item is low severity. Dead code54ContextMenuPortalUnreachable variable (0 lines)
Composition
Open the graphExplore this codebase
- Docs364 pages across 6 modules
- ChatAsk this codebase a question and get an answer with its sources.
- Files542 files with per-file docs, health and history
- ArchitectureDependency graph, layers, and 67 entry points
- Code healthPer-file scores, 670 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.