-
Notifications
You must be signed in to change notification settings - Fork 228
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Input PURL does not match output PURL #1274
Comments
Is this issue still open? |
@nikkuAg I think it is... @johnmhoran @TG1999 any input? Anyone working on this already? |
@nikkuAg you are welcome to work on this. |
Could you please explain this issue? |
VulnerableCode already uses/provides the package namespace correctly so there is nothing to fix here. The work is needed in SCTK - aboutcode-org/scancode-toolkit#3443 |
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Using the Package API to check for PURLs that are present and might have vulnerabilities, I discovered that for some PURLs like
pkg:deb/
, the actual correct name requires thedebian
namespace, which is missing.The text was updated successfully, but these errors were encountered: