-
Notifications
You must be signed in to change notification settings - Fork 22
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: Add support for npm Dependency Graph #187
Merged
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
Member
abhisek
commented
Jan 10, 2024
- refactor: Parser to use dependency graph parsers
- feat: Add npm package-lock.json graph parser
SafeDep OSS VetPolicy Checks
New Packages
Packages Violating Policy[Maven]
|
Deploying with Cloudflare Pages
|
abhisek
force-pushed
the
feat/npm-graph-parser
branch
9 times, most recently
from
January 14, 2024 18:40
ae2bdbd
to
5b0d2b2
Compare
feat: Add npm package-lock.json graph parser fix: Npm graph parser path to root traversal fix: File naming convention for npm graph parser feat: Add reporter for graph visualization in dot format feat: Add support for showing dependency upgrade path in summary report fix: Bug in summary reporter related to random ordering of entries with same score chore: Add support for experimental flag in scanner config refactor: Test cases or npm package name extractor into utils feat: Add support for dependency graph data in CSV report generator fix: LFP npm handle package links test: Improve test for npm name extraction feat: Add support for reconstructing dependency graph using insights data fix: purl reader to use package manifest builder test: Add E2E for gradle dependency graph reconstruction fix: Handle root node marking heuristics for enriched dependency graph feat: Allow query command to generate dependency graph fix: Scanner dependency graph reconstruction using dependency distance fix: Test case for maven dependency graph reconstruction chore: Improve summary report text for dependency path to root refactor: Code re-use in npm graph to find by semver range
abhisek
force-pushed
the
feat/npm-graph-parser
branch
from
January 14, 2024 18:51
5b0d2b2
to
1dba6fd
Compare
c0d3G33k
approved these changes
Jan 17, 2024
abhisek
force-pushed
the
feat/npm-graph-parser
branch
from
January 22, 2024 04:49
3f61da8
to
d0f6a82
Compare
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.