Software does not have a sense of elegance, and short of a strong AI, it cannot ever have a sense of elegance. The kind of technical debt that matters is mismatches between program abstractions and target domain abstractions. What this does is more like using a spell checker to determine how close a book is to being ready to publish - fundamentally misguided at best.
Nice. I would like to see inclusion of the following metrics:<p>1. Class coupling - amount of time it takes to grok the code<p>2. Build time (full, typical partial etc) - amount of time developer is twiddling his tumbs<p>3. Time between checkin, integration tests and end-user tests - amount of time code spent being created but not used, aka "waste" per The Toyota Way<p>4. Referential loops in layering diagram - amount of problems that need to be overcome to start refactoring