-
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
Incorrect downloadLocation for certain NPM packages #2129
Labels
Comments
kzantow
changed the title
Incorrect downloadLocation formats populated
Incorrect downloadLocation for certain NPM packages
Sep 14, 2023
This looks to have been addressed in the merged PR -- shout out if this isn't correct and we can reopen |
wagoodman
added
the
changelog-ignore
Don't include this issue in the release changelog
label
Feb 9, 2024
I am facing the same issue for NPM packages. The downloadLocation is not a proper URL and hence is failing the ntia-checker. Environment: Output of Sample Package info generated by syft
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
What happened:
We are seeing multiple instances where the downloadLocation is populated with either incorrect URL or incorrect format of the URL.
Example of incorrect URL:
Here the downloadLocation is not even a complete URL.
Example of incorrect URL format:
downloadLocation value
git@github.com:colorjs/color-name.git
does not comply with the accepted formats for Git by https://spdx.github.io/spdx-spec/v2.3/package-information/#77-package-download-location-fieldIn the same document for some packages the
Git
location is populated correctly so not sure why some are populated with incorrect format.What you expected to happen:
downloadLocation is one of the fields that is verified by https://github.com/spdx/ntia-conformance-checker and due to these issues the checks are failing.
Steps to reproduce the issue:
Anything else we need to know?:
Environment:
syft version
: v0.89.0cat /etc/os-release
or similar): Alpine Linux v3.16The text was updated successfully, but these errors were encountered: