Automate enumeration of dependencies' licences

[bryanchriswhite]

We need to be in a position to know with certainty what licenses apply at any given point in time to our code base. This information will likely have multiple applications and will need to be consolidated from multiple code repositories into a single source of truth; presently this (LA org) gdrive spreadsheet. To get the most out of this information it seems prudent that we categorize these by how we're using them; i.e. using, modifying, and/or distributing.

I imagine this looks something like writing a script that uses the appropriate package manager CLI to get a comprehensive list of all dependencies and their repo URLs. I think we'll want to be able to distinguish development and production dependencies as that informs us about how we're using those dependencies.

[hacklschorsch]

Maybe one of those are helpful? Or is this too enterprisey? https://reuse.software/comparison/