Repowise · Codebase intelligence
Cypress-Ink-Labs / family-events-backend
Does the health score find the bugs?
Repowise ranks every file by predicted defect risk. Of the 20 files it flags as riskiest, 20 (100%) actually needed a bug fix in the last 6 months — 3.8× better than picking files at random.
Languages
- json42.5%
- typescript27.6%
- sql16.9%
- markdown5.6%
- shell2.4%
- javascript2.3%
- dockerfile1.1%
Key modules14
- dockerfile
cleanup-stale
cron/cleanup-stale
- dockerfile
db-maintenance
cron/db-maintenance
- dockerfile
enrich-events
cron/enrich-events
- dockerfile
review-events
cron/review-events
scrape-sources
How Cypress-Ink-Labs/family-events-backend works
This page is an auto-generated, always-fresh map of the Cypress-Ink-Labs/family-events-backend repository, written primarily in json. 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 750 source files, 1,536 symbols, and 10 languages, structured as a monorepo with 14 packages. Git churn analysis flags 61 high-frequency files as hotspots — places where bugs, rewrites, and code review tend to concentrate. The dependency graph clusters into 529 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.