Code health
This codebase scores 7.1 out of 10 for code health, which we rate good. It also scores maintainability 8.1 and static performance 9.8 out of 10. The three are scored separately and never blended into one number. Risk is concentrated, as it usually is: 199 of 6,930 files are git hotspots, and they average 3.9 — which is where the fixes pay off most.
4 things worth doing this quarter.
Break up execute (CCN 24, 91 lines)
fineract-provider/src/main/java/org/apache/fineract/infrastructure/campaigns/jobs/executeemail/ExecuteEmailTasklet.java:75
execute nests its control flow deeply; 1 file imports it, changed 1 time in 90 days.
Break up fromParsedJson (CCN 34, 147 lines)
fineract-provider/src/main/java/org/apache/fineract/portfolio/loanaccount/service/LoanChargeAssembler.java:67
fromParsedJson nests its control flow deeply; 5 files import it.
Delete 149 unused symbols and files (2,122 lines)
Nothing in the graph reaches them, across 122 files; every reader and agent pays to skip them.
Break up modifyCalendar (CCN 25, 86 lines)
fineract-provider/src/main/java/org/apache/fineract/portfolio/loanaccount/service/LoanApplicationWritePlatformServiceJpaRepositoryImpl.java:369
modifyCalendar has many independent paths through it; 11 files import it.
Add a test coverage report
Without one, Repowise cannot tell tested code from untested code, so every test-related action says “unknown”.
Every detector's open count by area, each with its worst example. An inventory, not a to-do list: the actions above are the part worth doing.