Whenever I look at a new project on github, the first thing I do is try to get to the "core" of the source code, where the actual code that implements the basic

Whenever I look at a new project on github, the first thing I do is try to get to the "core" of the source code, where the actual code that implements the basic feature actually lives. One quality metric that I've noticed my brain has developed over the years is how deep in the directory hierarchy I have to dive to finally find some actual code amidst the mess of config files, readmes, yaml things, json metadata and various other crap that carry essentially no semantic. It's been surprising how accurately this metric measures the overall quality of the project. Large Java codebases are one of the worst offenders in that regard. Unfortunately by this metric, and independent of anything else, this project does not fare well at all ... I give you my first attempt at actually finding the code, depth= https://github.com/mnfst/manifest/blob/master/packages/core/admin/src/app/app.component.ts https://github.com/mnfst/manifest/blob/master/packages/core/... depth=6 below project top dir (ignoring github-added crap)