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

How are we handling sub-dependencies in the white list? #71

Closed
ominestre opened this issue Apr 4, 2022 · 1 comment
Closed

How are we handling sub-dependencies in the white list? #71

ominestre opened this issue Apr 4, 2022 · 1 comment
Assignees
Labels
question Further information is requested

Comments

@ominestre
Copy link
Owner

If a common shared dependency has as vulnerability that's taking a while to work through the ecosystem what happens when that is whitelisted in rotten-deps? Does the primary dependency still fail?

At minimum this should be elaborated on in the documentation.

@ominestre ominestre added the question Further information is requested label Apr 4, 2022
@ominestre ominestre self-assigned this Apr 4, 2022
@ominestre ominestre added this to Triage in Main Project Board via automation Apr 10, 2022
@ominestre ominestre moved this from Triage to Planned in Main Project Board Apr 10, 2022
@ominestre ominestre moved this from Planned to Doing in Main Project Board Apr 10, 2022
@ominestre
Copy link
Owner Author

When this question entered my head I was in the process of wrasslin' some yarn audit issues and was mixing up the goal of rotten-deps which is just outdated. It is difficult to determine something like eslint is only outdated because of a sub dependency so this isn't even a scenario I felt worth documenting.

Closing the question.

Main Project Board automation moved this from Doing to Done Apr 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
Development

No branches or pull requests

1 participant