Add support for resolving npm dependencies' licenses#48
Add support for resolving npm dependencies' licenses#48kezhenxu94 merged 2 commits intoapache:mainfrom
Conversation
zooltd
commented
Jul 23, 2021
- Parse the project package.json file to gather the required packages
- Run command 'npm install' to install or update the required node packages (can skip)
- Walk through each package's root directory to resolve licenses
- STEP 1: Try to find and parse the package.json file to capture the license field
- STEP 2: Try to find the license file to identify the license
|
You should update the doc to show how to use this. |
kezhenxu94
left a comment
There was a problem hiding this comment.
This is a very good start point to resolve dependencies’ licenses in NPM projects.
This PR only resolves the direct dependencies’ licenses, will you continue to resolve their transitive dependencies in next PR?
Glad to take it. Also, I'm planning to resolve dev-dependencies' licenses. |
|
Notice, dev-dependency is not binary level or source code level dependency. |
|
Dev-tool should not include commercial or unknown licenses. But even GPL and AGPL are fine to use, that is what I mean different. |
Got it. I will work on this feature in next PR. |