17
Large Files (500+ LOC)
19
High-Churn Files (50+)
0.9%
Churn Rate
75.8K
Total LOC
Monthly Churn Heatmap (Top Files)
0 changes
1-5
6-15
16-30
31-50
50+
File Size vs. Change Frequency
Largest Files (500+ Lines)
| File Path | Lines | Type | Concern |
|---|
Churn by Directory
How This Data Was Gathered
This visualization analyzes code churn patterns - the frequency and magnitude of file changes.
Data Sources
- Large files:
find src -name "*.tsx" -exec wc -l {} \; | awk '$1 > 500' - Change counts:
git log --all --pretty=format: --name-only | sort | uniq -c - Lines of code:
wc -lfor individual files
Understanding Churn
- High churn + Large size: Critical refactoring candidates
- High churn + Small size: May indicate poor abstraction or volatile requirements
- Low churn + Large size: Stable but may need splitting for maintainability
- Low churn + Small size: Healthy, focused modules
Recommendations
- Files in the upper-right quadrant (large + high churn) need immediate attention
- Test files with high churn indicate complex or unstable features
- Consider breaking files over 500 lines into focused modules
- Generated files (API models) have expected high churn and can be excluded from analysis
Data collected: January 05, 2026