-
Notifications
You must be signed in to change notification settings - Fork 588
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
Gemspec file generating empty SBOMs #1952
Comments
Hi @diptanshumittal, thank you for the report and the information necessary to reproduce this issue. We'll take a look when we are able. |
👋 hey @diptanshumittal! It looks like it's enabled only for the image cataloger by default syft/syft/pkg/cataloger/cataloger.go Lines 42 to 62 in a90cff1
Can you try updating your configuration code to enable that cataloger. See the configuration here: |
Depending on where the
**/specifications/**/*.gemspec , but if the gem is defined in the directory being scanned, for example, I'm not sure that the gemspec would be under the specifications directory.
See also #2128 |
I think this might solve the confusion with this pr/comment, but it's not clear if it is being currently updated or is stale |
I believe this is fixed thanks to #1971 so I'll close this issue, but feel free to re-open if you are still having problems. Thanks! |
What happened:
Empty SBOMs are generated using the *.gemspec file. Syft is not able to detect any package using the gemspec file even tough gemspec is a valid cataloger.
What you expected to happen:
Expected the SBOMs to atleast have a single package with gem details in it. Similar to other languages like Javascript.
Steps to reproduce the issue:
Run
syft packages -o spdx-json
for the fileAnything else we need to know?:
Environment:
syft version
: 0.85.0cat /etc/os-release
or similar): macOS 13.4.1The text was updated successfully, but these errors were encountered: