Oh, I've got your concern. By uselessness, I mean parts of your code that are not used in other parts of your app. So, it's not a comparison with other tools, it's not an attempt to estimate the usefulness of them. It's just a tip - " Hey, look at this code, looks like you do not use it anywhere in your project ". The same for 'Zone of Pain' - it's a code that used a lot in other parts of your app, and changing this code could have a big impact on the whole project - could bring some pain. I totally need to provide more information about the concepts of this measurement for users. Most of them I borrowed from the "Clean Architecture" book of Robert C. Marin. And probably I need to remove the Score at all or leave it only for personal projects of users that are not visible for everyone. Score is not for the comparison it's like a health indicator, tracking it you can be sure that your project is Ok. Thank you Dharmen Shah you give me a more clear understanding of this project.

Thanks a million! :-)

That's the good question. Score mainly based on percent of components in the Zone of Pain because it makes your project harder to develop and change, and also Score take into account total amount of files, dependencies and unused code. I think it could worth a separate article or blog post about the way how to improve Score, what it means, and how it's calculated. I never though about analysis of production or distribution files. I saw this project as a way to track Architecture Quality of source code during the dev process. But actually, it does not matter where code comes from, I think, I can support npm as well as git repositiries.

Thank you Dinys, Yes you're right it pretty short now. I'm about to add more detailed explanations of every suggestion with a link to corresponding articles and best practices. I do not have any special twitter account for this project, just use my own account.