@Vampire Thinking more on the subject. CI stats, code coverage over time. This could exist actually if gradle wanted it to. ie. only stats for projects built are kept in stored over time so you ‘could’ in theory go into any libraries history just fine. Each lib has it’s own build time in a monorepo as well. Each lib has it’s own code coverage. All that could simply be stored on cases where it is actually built. I guess my plea above is for better monorepo support like github is doing. The codeowners file rocks as people work cross team and it just tags the teams of the code you touched mapping code to team easily.