-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(nodejs): parse package.json files alongside package-lock.json for licenses #2916
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Hey @DmitriyLewen, |
Hello @naortalmor1 |
This PR is stale because it has been labeled with inactivity. |
github-actions
bot
added
the
lifecycle/stale
Denotes an issue or PR has remained open with no activity and will be auto-closed.
label
Dec 29, 2022
knqyf263
added
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
and removed
lifecycle/stale
Denotes an issue or PR has remained open with no activity and will be auto-closed.
labels
Jan 23, 2023
Any updates on this? |
@DmitriyLewen Now, we can use post-analyzers like poetry. Would you rewrite this PR? |
DmitriyLewen
changed the title
feat(fs): merge licenses from package.json from node_modules folder to package-lock.json
feat(node): parse package.json files alongside package-lock.json
Mar 1, 2023
DmitriyLewen
changed the title
feat(node): parse package.json files alongside package-lock.json
feat(nodejs): parse package.json files alongside package-lock.json
Mar 1, 2023
knqyf263
approved these changes
Mar 15, 2023
knqyf263
changed the title
feat(nodejs): parse package.json files alongside package-lock.json
feat(nodejs): parse package.json files alongside package-lock.json for licenses
Mar 16, 2023
atombrella
pushed a commit
to atombrella/trivy
that referenced
this pull request
Mar 25, 2023
…quasecurity#2916) Co-authored-by: knqyf263 <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
package-lock.json
files do not contain dependency license information.This PR parses
*/node_modules/<package_name>/package.json
files alongsidepackage-lock.json
and identify licenses.Checklist