repowise-dev/repowise

Codebase intelligence for AI and humans: code health scores, auto-generated docs, git analytics, dead code detection, and architectural decisions via MCP.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 4 minutes ago
Added to GitGenius on September 10th, 2026
Created on March 23rd, 2026
Open Issues & Pull Requests: 164 (+0)
GitHub issues: Enabled
Number of forks: 690
Total Stargazers: 6,414 (+0)
Total Subscribers: 28 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 11.2 hours
Mean response time: 2.8 days
90th percentile: 6.9 days
Tracked items: 350

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 79% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "bug" is answered fastest, typically in about 4 hours, while "enhancement" waits about 25 hours. Almost all tracked open issues have seen activity in the last three months. Only 11% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 63
New in 7 days: 19
Closed in 7 days: 29
Avg open age: 38 days
Stale 30+ days: 8
Stale 90+ days: 5

Recent activity

Opened in 7 days: 15
Closed in 7 days: 22
Comments in 7 days: 4
Events in 7 days: 14

Top labels

  • bug (171)
  • good first issue (56)
  • help wanted (47)
  • enhancement (41)
  • documentation (3)

Detailed Description

Repowise is a codebase intelligence tool that provides code health scores, auto-generated documentation, git analytics, dead code detection, and architectural decision tracking through a Model Context Protocol interface.

The tool addresses the challenge of understanding and maintaining large codebases by combining multiple analysis approaches. It computes code health scores to quantify codebase quality, generates documentation automatically to keep it in sync with actual code, analyzes git history to surface patterns and trends, identifies unused code segments that accumulate technical debt, and captures architectural decisions in a queryable format. The Model Context Protocol integration allows both AI systems and human developers to access these insights programmatically, making the intelligence available to language models and custom tooling.

Repowise suits teams managing complex codebases who want visibility into code quality without manual auditing. It works well for projects where documentation tends to drift from implementation, where technical debt tracking is difficult to maintain, or where onboarding new developers requires understanding both current architecture and historical decisions. The combination of static analysis, git-based insights, and decision tracking makes it particularly valuable for teams using AI-assisted development, since the MCP interface feeds codebase context directly to language models.

The project shows active development with regular commits across multiple areas of the codebase. Work spans the core analysis engine, the MCP server implementation, documentation generation, and the web interface. The maintainers have established a public roadmap and respond to issues, indicating ongoing commitment to the tool's evolution. The project maintains a clear separation between analysis modules and integration points, suggesting a focus on extensibility and allowing different components to be used independently or combined.