repowiserepowise
Sign in
FaserF/ShieldDNS
OverviewDocsArchitectureKnowledge GraphFilesCode HealthRefactoring

People & History

CommitsContributorsDecisions
Chat
Stats
repowiserepowise
ExplorePricingDocs
Sign in
repowiseFaserF/ShieldDNS

FaserF / ShieldDNS

ShieldDNS is a lightweight, efficient, and privacy-focused DNS over HTTPS (DoH) and DNS-over-TLS (DoT) proxy

Go4github.com/FaserF/ShieldDNS
Indexed at09b5b8c·13d ago·Up to date with upstream
Open dashboardChat with repo

Code health

5.0out of 10Needs work

FaserF/ShieldDNS scores 5.0 out of 10 on defect risk, which Repowise rates Needs work. Maintainability scores 6.7 out of 10. Static performance risk scores 9.4 out of 10. The three are scored separately and never blended into a single number. 11 of 103 files are git hotspots, the places where changes and bug fixes concentrate.

Full health report
Defect risk5.0/10 · Needs work
Maintainability6.7/10 · Fair
Performance risk9.4/10 · Excellent
Files
103
Symbols
683
Modules
4
Doc pages
110
Dead exports
0

Where the risk concentrates

All 11 hotspots

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

FileChurnPrior fixesMaintainersCommits 90d
main.goadmin97.2th %ile23bug magnet213
dns.goadmin98.6th %ile20bug magnet1bus factor 15
config.goadmin93.1th %ile18bug magnet1bus factor 115
events.jsadmin/www/admin/js/ui94.4th %ile17bug magnet1bus factor 110
renderers.jsadmin/www/admin/js/ui90.3th %ile13bug magnet1bus factor 19
api_utils.goadmin91.7th %ile9bug magnet1bus factor 13

Read more about FaserF/ShieldDNS

  • OverviewFiles, symbols, languages, packages, git intelligence
  • ArchitectureDependency graph, layered architecture, symbol index, and third-party dependencies
  • Code healthPer-file health scores, hotspots, test coverage, dead code, and refactoring targets
  • AI explanationsProModule-by-module documentation generated from source
  • CommitsChange-risk ranked history with AI-agent provenance and hotspots
  • ContributorsBus-factor, per-file maintainer maps, and human/agent collaboration
  • DecisionsArchitectural decisions extracted from commits and PRs
  • Chat with this repoSign inAsk grounded questions over the indexed code

Add a badge to your README

Both badges are public, cached, and update on their own after every index. Nothing to install.

Repowise badge

Links to this page. Adding it also re-indexes the repo every week.

Repowise badge: explore code
[![repowise](https://api.repowise.dev/badge/wiki/FaserF/ShieldDNS.svg)](https://repowise.dev/repo/FaserF/ShieldDNS)

Code health badge

Average health across every file, straight from the latest index.

Code health badge showing the average health score out of 10
[![Code health](https://api.repowise.dev/badge/health/FaserF/ShieldDNS.svg)](https://repowise.dev/repo/FaserF/ShieldDNS)

How FaserF/ShieldDNS works

ShieldDNS is a lightweight, efficient, and privacy-focused DNS over HTTPS (DoH) and DNS-over-TLS (DoT) proxy This page is an auto-generated, always-fresh map of the FaserF/ShieldDNS repository, written primarily in Go. Repowise indexes the source, parses every symbol, computes a dependency graph, scores per-file code health from complexity, duplication, test coverage and churn, mines git history for hotspots and ownership, and lifts the resulting architectural decisions into a wiki you can read or query through MCP.

The codebase has 103 source files, 683 symbols, and 9 languages, organised into 4 modules, led by go, javascript, yaml. Static analysis leaves 813 open findings across the three health dimensions.

Use the links above to open the interactive dashboards, or connect this repo to your editor via the Repowise MCP server for grounded answers inside Claude, Cursor, or VS Code.