Code health
This codebase scores 7.6 out of 10 for code health, which we rate good. It also scores maintainability 7.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: 73 of 4,839 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 safe_load_namespace (CCN 32, 118 lines)
src/prefect/utilities/importtools.py:441
safe_load_namespace nests its control flow deeply, and part of it is duplicated, so splitting it also removes a copy; changed 1 time in 90 days.
Flatten the nesting in bulk_create_flow_runs_from_deployment
src/prefect/server/api/deployments.py:1038
bulk_create_flow_runs_from_deployment nests its control flow deeply, and part of it is duplicated, so splitting it also removes a copy; changed 1 time in 90 days.
Delete 173 unused symbols and files (7,506 lines)
Nothing in the graph reaches them, across 77 files; every reader and agent pays to skip them.
Break up run (CCN 19, 78 lines)
src/integrations/prefect-redis/prefect_redis/messaging.py:520
run nests its control flow deeply, and part of it is duplicated, so splitting it also removes a copy; changed 2 times in 90 days.
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.