-
Notifications
You must be signed in to change notification settings - Fork 576
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
Add ability to see the first location a package was added #1724
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Alex Goodman <alex.goodman@anchore.com>
Benchmark Test ResultsBenchmark results from the latest changes vs base branch
|
May I know why this pr is not merged . Its extremely helpful in deduping the components across layers |
do you have an eta for this addition? can be helpful |
Hi @tomerse-sg and @Deep232, thanks for the notes, we don't have an ETA but we will take a look and see if we can move this forward. Thank you for letting us know this would be useful for you! |
can you please elaborate about the problem you specified in the PR description? |
I tried to run a test using an image golang 1.14 using all-layers and squashed-with-all-layers. |
another question - seems this pr is based on syft 0.76.0, do you think it is possible to contribute new pr and aligned it to newest syft? another thing - I think I've found a bug -
and when I scan it I do see "jq" |
I think this solve the problem of the deleted package - #3138 |
Adds a
squashed-with-all-layers
resolver which acts like the squashed resolver with the additional behavior of returning instances of the path found in all other layers. This, combined with additional changes to denote the layer index directly in locations, allows for someone to be able to know the first location a package was introduced.For example:
When running syft...
You'll see merged location elements for each package:
TODO:
Open question:
Problems:
Closes #435