slopmeter · scanned 2026-09-10
Graphify-Labs/graphify scores grade D, 63 of 100.
Over-engineering is what costs the grade: 147 findings · py 3.0/kLOC · rust 0.0/kLOC · csharp 9.7/kLOC.
Against established software: 48% — above 13 of the 27 hand-written public projects in slopmeter's corpus, scanned 2026-09-10. A sample, not a census.
What was parsed
| language | lines | findings / kLOC | parser |
|---|---|---|---|
| python | 48,424 | 3.0 | tree-sitter |
| csharp | 103 | 9.7 | tree-sitter |
| rust | 0 | 0.0 | tree-sitter |
Commits
955 first-parent commits on v8 in the window, lockfiles and build output excluded. Median 67 lines, p90 339, 71 over 400 lines, p90 5 files per commit, churn proxy 16%.
How this was measured
Over-engineering is five patterns counted per thousand lines, parsed with go/types and tree-sitter rather than matched as text. Test coverage is logic files against whole-word mentions of their symbols in the test files beside them. Commit health reads git log --first-parent over the window, with lockfiles and build output excluded. The composite renormalises over whatever could be measured; anything that could not says so.
Run the same scan yourself — it clones into a temporary directory and removes it afterwards:
slopmeter github Graphify-Labs/graphifyThe file-level findings are not published here. slopmeter prints them for the people who can act on them; this page carries the aggregates they rest on.