How to prevent duplicate package names: jinja2 and Jinja2 ?
Maybe we can build a more human path instead of full with .venv/........ ?
Because when we opened a vulnerability by specific dependency.
GitHub UI is building a path to a dependency that doesn't exist: https://github.com/<ORG_NAME>/<REPO_NAME>/blob/-/.venv/lib/python3.9/site-packages/protobuf-3.19.4.dist-info/METADATA
Maybe we can refer to package / repo that contains jinja ? package_name@jinja
Do we have a plan to add indirect dependencies for Github format ?
What happened:
How to prevent duplicate package names:
jinja2
andJinja2
?Maybe we can build a more human path instead of full with
.venv/........
?Because when we opened a vulnerability by specific dependency.
GitHub UI is building a path to a dependency that doesn't exist:
https://github.com/<ORG_NAME>/<REPO_NAME>/blob/-/.venv/lib/python3.9/site-packages/protobuf-3.19.4.dist-info/METADATA
Maybe we can refer to package / repo that contains jinja ?package_name@jinja
indirect
dependencies for Github format ?What you expected to happen:
Steps to reproduce the issue: Github workflow
Anything else we need to know?:
Environment:
syft version
: