You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When generating SBOM for a directory, all download location values are "NOASSERTOIN", even if the ecosystem is Javascript/NPM
What you expected to happen:
We should see download location values (URL) in the generated SBOM file.
Take package @pkgjs/parseargs as an example, it has url, so in the SBOM file we should see the value for download locatoin as [email protected]:pkgjs/parseargs.git
run 'npm install' in the folder of the cloned repo
run syft, in my case the command is 'syft C:\test-syft\javascript -o spdx-json > test-after-npm-install.json'
open the generated SBOM file (attached) with an editor/IDE, search ' "downloadLocation": " ', see the count
search ' "downloadLocation": "NOASSERTOIN" ', the count is the same as the previous count, which means all the download location values are "NOASSERTION"
Anything else we need to know?:
Not sure if I should call it a bug or it is expected behavior. If it is expected behaviour, could you please let me know? Thanks!
To give more context, after checking the code, I feel Syft is running in this way:
(This only applies to the JavaScript ecosystem, haven't looked into other ecosystems yet, of course lots of work will be done for other ecosystems)
if scanning a directory, the cataloger will check package-lock.json
if scanning an image, the cataloger will check package.json
What happened:
When generating SBOM for a directory, all download location values are "NOASSERTOIN", even if the ecosystem is Javascript/NPM
What you expected to happen:
We should see download location values (URL) in the generated SBOM file.
Take package @pkgjs/parseargs as an example, it has url, so in the SBOM file we should see the value for download locatoin as [email protected]:pkgjs/parseargs.git
"repository": {
"type": "git",
"url": "[email protected]:pkgjs/parseargs.git"
}
Steps to reproduce the issue:
Anything else we need to know?:
Not sure if I should call it a bug or it is expected behavior. If it is expected behaviour, could you please let me know? Thanks!
Github does not support uploading json file, so sharing it with the Google drive link:
https://drive.google.com/file/d/1kUxQFMoihrpOXvwxt5di6Mv7BXnWSLcN/view?usp=sharing
Environment:
syft version
: 0.89.0cat /etc/os-release
or similar): Microsoft Windows [Version 10.0.19045.3324]The text was updated successfully, but these errors were encountered: