There is an awful lot of this: /\** \* Checks if a library is excluded. \* \* @param library the library to check \* @return true

There is an awful lot of this: /\** \* Checks if a library is excluded. \* \* @param library the library to check \* @return true if the library is excluded, false otherwise \*/ protected boolean isLibraryExcluded(Library library) { return library.getName().equals("Spring Boot"); } The comment adds nothing - I'm still confused what this one line function is meant to do or what the word "excluded" means in this context. The thought definitely occurs that whatever comment value can be generated automatically could also (and perhaps should instead) be done locally for the viewer, rather than actually being stored in the codebase. Then it doesn't clutter up the codebase, and also can't get out of sync. Or since these comments are really JSDoc style comments, they could be applied just before documentation is generated.