Repowise · Codebase intelligence
A collection of lightweight, strongly-typed TypeScript utility libraries — schema validation with type inference, async helpers, deep object operations, object mapping, job scheduling, and more.
Repowise ranks every file by predicted defect risk. Of the 20 files it flags as riskiest, 16 (80%) actually needed a bug fix in the last 6 months — 4.8× better than picking files at random.
todo-backend
demos/todo-backend
todo-frontend
demos/todo-frontend
async
libs/async
auth
libs/auth
benchmarks
A collection of lightweight, strongly-typed TypeScript utility libraries — schema validation with type inference, async helpers, deep object operations, object mapping, job scheduling, and more. This page is an auto-generated, always-fresh map of the cleverbrush/framework 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 868 source files, 2,791 symbols, and 8 languages, structured as a monorepo with 26 packages. Git churn analysis flags 85 high-frequency files as hotspots — places where bugs, rewrites, and code review tend to concentrate. The dependency graph clusters into 265 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
libs/benchmarks
client
libs/client
deep
libs/deep
di
libs/di
env
libs/env
knex-clickhouse
libs/knex-clickhouse
knex-schema
libs/knex-schema
log
libs/log