repowiserepowise
Sign in

Repository

HexSleeves/kata-machine
OverviewDocsArchitectureKnowledge GraphFilesCode HealthRefactoring

People & History

CommitsChange CouplingContributorsDecisions
ChatPro
By the Numbers
repowiserepowise
ExplorePricingDocs
Sign inIndex repoIndex your repo free
repowiseHexSleeves/kata-machine

Repowise · Codebase intelligence

HexSleeves / kata-machine

typescriptgithub.com/HexSleeves/kata-machine
Indexed at1ea843c·14h ago·Up to date
Open dashboardChat with repo
Files indexed
46
Symbols
46
Languages
4
Structure
Single

Languages

  • typescript80.4%
  • javascript13.0%
  • json4.3%
  • markdown2.2%

Explore HexSleeves/kata-machine

Overview

Files, symbols, languages, packages, git intelligence

Code health

Full report
85/100
Healthy0 hotspots
  • Code health96
  • Dead code74
  • Hotspot density100
  • Bus factor1

How HexSleeves/kata-machine works

This page is an auto-generated, always-fresh map of the HexSleeves/kata-machine 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 46 source files, 46 symbols, and 4 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 41 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.

Architecture

Dependency graph, layered architecture, symbol index, and third-party dependencies

Code health

Per-file health scores, hotspots, test coverage, dead code, and refactoring targets

AI docsPro

Module-by-module documentation generated from source

Commits

Change-risk ranked history with AI-agent provenance and hotspots

Contributors

Bus-factor, per-file maintainer maps, and human/agent collaboration

Decisions

Architectural decisions extracted from commits and PRs

Chat with this repoSign inPro

Ask grounded questions over the indexed code