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

Output dependency graph to identify source of bad license that triggered fails-on. #197

Open
shengy90 opened this issue Jun 25, 2024 · 0 comments

Comments

@shengy90
Copy link

For instance I'd like to flag GNU/ GPL licenses in my dependency.

Right now --fail-on fails on the first instance of a dependency that uses GNU/GPL license. The only way to troubleshoot right now is to:

  • Use alternative library like https://github.com/tox-dev/pipdeptree to detect how this dependency come about in the first place, then uninstall the source dependency
  • Or uninstall it one by one until no more flags are raised which is not a good solution.

It'd be great if we could identify all failed dependencies (not just the first one) and identify the sources so we can get rid of the incompatible ones!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant