In addition to report files as a major then packages as a minor, it would be rather useful to report also or instead a package as a major and which path (typically a dir) or path(s) (for a whole tree) this package is in.
This would become a top-level packages attribute in the scan results.
In the end there are two ways to look at a codebase:
- a bunch a files some of them part of a package or not. Some of them with a license, copyright, etc...
- OR a bunch of packages (each being a logical breakpoint in the codebase tree) with some files... and other files that are not found part of a package.
When I review things, I would likely set aside all the files part of a package and look only by exceptions at things that are not part of one. Reporting scanned by package would help a lot to focus on exceptions.
In addition to report files as a major then packages as a minor, it would be rather useful to report also or instead a package as a major and which path (typically a dir) or path(s) (for a whole tree) this package is in.
This would become a top-level
packagesattribute in the scan results.In the end there are two ways to look at a codebase:
When I review things, I would likely set aside all the files part of a package and look only by exceptions at things that are not part of one. Reporting scanned by package would help a lot to focus on exceptions.