Codebase Health Score

How This Data Was Gathered

This health score analyzes 4,868 TypeScript/TSX files across the Acme frontend codebase.

Data Sources

• Total files: find src -name "*.ts" -o -name "*.tsx" | wc -l = 4,868
• High-churn files (50+ changes): git log --pretty=format: --name-only | sort | uniq -c | awk '$1 >= 50' | wc -l = 19
• Large files (500+ lines): find src -name "*.tsx" -exec wc -l {} \; | awk '$1 > 500' | wc -l = 17
• Contributors: git log --format="%an" | sort -u | wc -l = 69
• TODO/FIXME count: grep -r "TODO\|FIXME" src --include="*.tsx" | wc -l = 1,546
• console.log count: grep -r "console.log" src --include="*.tsx" | wc -l = 80
• any type count (non-generated): grep -r ": any" src --include="*.tsx" --exclude-dir=generated | wc -l = 45

Score Calculation

• Stability: 100 - (highChurnFilesPercent x 200) = 100 - (0.39% x 200) = 22
• Maintainability: 100 - (largeFilesPercent x 100) = 100 - (0.35% x 100) = 65
• Code Quality: 100 - (any x 0.5) - (TODO x 0.02) - (console.log x 0.1) = 100 - 22.5 - 30.9 - 8 = 39
• Collaboration: Based on contributor count (capped at 100)
• Overall: Weighted average (Stability 25%, Maintainability 25%, Code Quality 20%, Collaboration 15%, Test Coverage 15%)

Assumptions

• Files with 50+ changes in the repository history are considered "high-churn"
• Files over 500 lines are considered "large" and potentially complex
• Higher contributor count indicates better knowledge distribution
• Generated API code is included in metrics but has limited impact

Data collected: January 05, 2026