takenet / deckard
gomain38ada4311.6K linessynced 1d ago
Code health
8.8out of 10Excellent
This codebase scores 8.8 out of 10 for code health, which we rate excellent. It also scores maintainability 8.5 and static performance 9.9 out of 10. The three are scored separately and never blended into one number. Risk is concentrated, as it usually is: 2 of 108 files are git hotspots, and they average 4.1 — which is where the fixes pay off most.
Do next
Nothing stands out this week.
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
- 11.6K
Recent activity
All commitsCommits
No commits indexed yet.
Decisions
- change queue removal order to prevent orphaned storage dataproposed · 1d ago
- do not reset message score on Nackproposed · 1d ago
- use Redis SCAN instead of KEYS to avoid blockingproposed · 1d ago
- upgrade gRPC/protobuf/OpenTelemetry to patch critical CVEproposed · 1d ago
- Use getWithFallback parsing path for consistent comparisons and duration parsingproposed · 1d ago
- Fix config getter override logic for Viper aliasesproposed · 1d ago
Everything we found
161 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 health87Co-change scatter · internal/queue/cache/redis_cache.go12 findings · 5.9 deducted
- worst item is low severity. Refactoring10main+0.6 health, S effort · examples/golang/example.go
- worst item is medium severity. Decisions9internal/queue/cache/redis_cache.go7 awaiting review · 2 hotspots ungoverned
- worst item is medium severity. Ownership55internal/queue/cache/redis_cache.go85% single-owner concentration, 3 commits in 90d
Composition
Open the graphgo 93%
csharp 1%dockerfile 1%java 1%makefile 1%Other 1%
Explore this codebase
- Docs119 pages across 4 modules
- ChatAsk this codebase a question and get an answer with its sources.
- Files108 files with per-file docs, health and history
- ArchitectureDependency graph, layers, and 2 entry points
- Code healthPer-file scores, 153 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.