Skip to content
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

Path to the victimized dependency #21

Open
mbiarnes opened this issue May 19, 2014 · 3 comments
Open

Path to the victimized dependency #21

mbiarnes opened this issue May 19, 2014 · 3 comments
Assignees
Milestone

Comments

@mbiarnes
Copy link

Is it possible to print the path to the victimized dependency when it fails the build due to a vulnerability instead only the name of the dependency?
In some cases it is very difficult to find this dependency.

@nealharris
Copy link

+1 I have some code for which victims-enforcer complains of a dependency that I'm quite sure my code doesn't even depend on.

@abn
Copy link
Member

abn commented Jun 6, 2014

@nealharris it might be a dependency of a dependency or some level down fwiw.

@gcmurphy I am thinking something like this maybe?

@gcmurphy
Copy link
Contributor

gcmurphy commented Jun 6, 2014

Yep. I think that's a good idea. I'll look into how I can do that.

On 6 Jun 2014, at 6:58 pm, Arun Babu Neelicattu notifications@github.com wrote:

@nealharris it might be a dependency of a dependency or some level down fwiw.

@gcmurphy I am thinking something like this maybe?


Reply to this email directly or view it on GitHub.

@gcmurphy gcmurphy added this to the 1.3.5 milestone Jun 9, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants