For now, using the tool requires some sort of expertise. A user should understand the differences between the license types (e.g. permissive, weak copyleft, strong copyleft, "copyleft over the network") in order to understand the consequences for the project he/she check the dependencies for.
We need to "transfer" some expertise to the tool itself by supporting:
-
a project license (e.g. Proprietory)
-
a project distribution profile (e.g. mobile-app)
-
project dependencies with their license names/types (already implemented at the time of writing)
-
returning/detecting required actions e.g.:
-
add the original copyright notice
-
disclose the source code
-
(re)-license the project under the same or compatible strong-copyleft license