repowiserepowise
Sign in
FaserF/ShieldDNS
OverviewDocsArchitectureKnowledge GraphFilesCode HealthRefactoring

People & History

CommitsContributorsDecisions
ChatPro
Stats
repowiserepowise
ExplorePricingDocs
Sign inIndex repoIndex your repo free
repowiseFaserF/ShieldDNS
SH
SH

FaserF / ShieldDNS

gomain2ad7e6922.8K linessynced 2h ago

Code health

5.2out of 10Fair

This codebase scores 5.2 out of 10 on defect risk, which we rate fair. It also scores maintainability 7.1 and static performance risk 9.4 out of 10. The three are scored separately and never blended into one number. The files you change most are the weak spot: 9 of 100 files are git hotspots, and they average 1.5.

Full health report →
Documentation106pages0 with model-written prose, 106 built from the indexScore validation19/202.16× baselineOf the 20 lowest-health files, 19 were bug-fixed in the last 6 months — 2.16× the 44% baselineDead code2exportsUnused exports that nothing in the graph reaches
Lines of code
22.8K
Files
100
Symbols
652
Modules
4
Languages
9

Recent activity

All commits →

Commits

No commits indexed yet.

Decisions

  • Implement structured slog logging and optimize sqlite performanceproposed · 2h ago
  • Reset cache and disable DB to force atomic counter fallbackproposed · 2h ago
  • Override GeoIP with mock to avoid network lookups in testsproposed · 2h ago
  • Use temp directory for test data to avoid writing to system pathsproposed · 2h ago

Needs attention

25 open
  • medium severity. ProposedImplement structured slog logging and optimize sqlite performanceAuto-proposed decision awaiting review
  • medium severity. ProposedReset cache and disable DB to force atomic counter fallbackAuto-proposed decision awaiting review
  • medium severity. ProposedOverride GeoIP with mock to avoid network lookups in testsAuto-proposed decision awaiting review
  • medium severity. ProposedUse temp directory for test data to avoid writing to system pathsAuto-proposed decision awaiting review
  • medium severity. Ungovernedadmin/api_system.goHigh-churn file with no governing decision

Where the risk concentrates

All 9 hotspots →

Ranked by prior bug fixes and change frequency, mined from full git history rather than from the code alone.

FileChurnPrior fixesMaintainersCommits 90d
dns.goadmin98.6th19bug magnet1bus factor 14
main.goadmin97.1th22bug magnet29
events.jsadmin/www/admin/js/ui94.3th17bug magnet1bus factor 17
config.goadmin92.9th17bug magnet1bus factor 112
renderers.jsadmin/www/admin/js/ui90.0th13bug magnet1bus factor 16

Composition

Open the graph →
go 44%javascript 21%yaml 13%json 8%markdown 5%Other 9%

Explore this codebase

  • Docs106 pages across 4 modules→
  • ChatAsk this codebase a question and get an answer with its sources→
  • Files100 files with per-file docs, health and history→
  • ArchitectureDependency graph, layers, and 7 entry points→
  • Code healthPer-file scores, 663 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→