Code health
This codebase scores 8.9 out of 10 for code health, which we rate excellent. It also scores maintainability 8.9 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: 24 of 9,481 files are git hotspots, and they average 4.9 — which is where the fixes pay off most.
4 things worth doing this quarter.
Break up __init__ (CCN 40, 159 lines)
platform/broadcom/sonic-platform-modules-micas/common/lib/plat_hal/chassisbase.py:49
__init__ nests its control flow deeply, and part of it is duplicated, so splitting it also removes a copy; 3 files import it, changed 1 time in 90 days.
Break up schema_validation (CCN 18, 52 lines)
platform/pddf/i2c/utils/pddfparse.py:1677
schema_validation nests its control flow deeply; 15 files import it, changed 2 times in 90 days.
Delete 10,432 unused symbols and files (344,996 lines)
Nothing in the graph reaches them, across 2,836 files; every reader and agent pays to skip them.
Flatten the nesting in getETValue
device/micas/x86_64-micas_m2-w6920-32qc2x-r0/monitor.py:329
getETValue nests its control flow deeply, and part of it is duplicated, so splitting it also removes a copy.
Add a test coverage report
Without one, Repowise cannot tell tested code from untested code, so every test-related action says “unknown”.
No commits indexed yet.
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.