Repowise · Codebase intelligence
A beautiful, calm, trust-building security dashboard that helps consumers understand and respond to vulnerabilities in their connected devices including smart home, IoT, mobile, laptops, routers, automotive, and health devices · Built with Manus
Repowise ranks every file by predicted defect risk. Of the 20 files it flags as riskiest, 6 (30%) actually needed a bug fix in the last 6 months — 4.8× better than picking files at random.
A beautiful, calm, trust-building security dashboard that helps consumers understand and respond to vulnerabilities in their connected devices including smart home, IoT, mobile, laptops, routers, automotive, and health devices · Built with Manus This page is an auto-generated, always-fresh map of the bmsull560/sentinel-home repository, written primarily in TypeScript. 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 145 source files, 643 symbols, and 7 languages. Git churn analysis flags 0 high-frequency files as hotspots — places where bugs, rewrites, and code review tend to concentrate. The dependency graph clusters into 32 tightly-coupled module communities.
Use the panels 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.
Files, symbols, languages, packages, git intelligence
Dependency graph, layered architecture, symbol index, and third-party dependencies
Per-file health scores, hotspots, test coverage, dead code, and refactoring targets
Module-by-module documentation generated from source
Change-risk ranked history with AI-agent provenance and hotspots
Bus-factor, per-file maintainer maps, and human/agent collaboration
Architectural decisions extracted from commits and PRs
Ask grounded questions over the indexed code