Code health
This codebase scores 6.5 out of 10 for code health, which we rate fair. It also scores maintainability 7.2 and static performance 9.9 out of 10. The three are scored separately and never blended into one number. Risk is concentrated, as it usually is: 6 of 454 files are git hotspots, and they average 3.6 — which is where the fixes pay off most.
3 things worth doing in the week to Sep 23, the last indexed commit, 3 of them now.
Simplify stripSchemaTypeIdentifiers in src/GraphQL/ParseGraphQLServer.js while the change is fresh
1 commit in the last 7 days added or worsened 1 critical or high finding here, still open. Fixing now costs less than after the next change.
Start breaking up matchesKeyConstraints (CCN 81, 233 lines): first lift lines 354-371
src/LiveQuery/QueryTools.js:354
matchesKeyConstraints is complex and keeps changing, and part of it is duplicated, so splitting it also removes a copy; 2 files import it.
Start breaking up buildWhereClause (CCN 142, 551 lines): first lift lines 497-556
src/Adapters/Storage/Postgres/PostgresStorageAdapter.js:497
buildWhereClause is complex and keeps changing, and part of it is duplicated, so splitting it also removes a copy; 3 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.