-
Notifications
You must be signed in to change notification settings - Fork 599
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: rather than have a hard max recursive depth - syft should detect parent pom cycles #2284
Comments
Actually, I revisited this behavior in #2769 and disabled the depth check by default, since the code was already checking for cycles, so I think this can be considered fixed by that PR. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What would you like to be added:
Syft currently has a hard coded cut off for max recursive depth for searching for a parent pom. There is some room where the code could be written to detect cycles, but it was unclear at the time of writing the pom parent look up if that cycles can be exited in this way.
Why is this needed:
More options of searching maven for pom documents with the correct information
Additional context:
#2274 (comment)
The text was updated successfully, but these errors were encountered: