Replies: 5 comments 1 reply
-
Created https://issues.redhat.com/browse/PROJQUAY-5100 to track this request. |
Beta Was this translation helpful? Give feedback.
-
Is this arbitrary ruby, or is it line-oriented? I guess what I'm really asking is: how much of a ruby parser we need? |
Beta Was this translation helpful? Give feedback.
-
Okay, I refuse to re-inflict the braindamage of reading |
Beta Was this translation helpful? Give feedback.
-
Started a draft PR: #836 |
Beta Was this translation helpful? Give feedback.
-
This was completed in #836 |
Beta Was this translation helpful? Give feedback.
-
Background
ACS's scanner supports scanning Ruby Gemspec files for vulnerabilities. ACS is looking to add this ability to ClairCore.
ClairCore now has the ability to obtain language-specific vulnerability data from OSV. OSV's database includes Ruby data, so ClairCore has a datasource for Ruby packages.
Proposal
ACS's Ruby Gemspec scanning support is pretty straightforward. Simply look for a regular file whose path adheres to the following regexp:
".*specifications/.*\.gemspec"
.An example file is as follows:
We simply care about
name
andversion
, both of which are required fields. Once those are determined, we may determine the related vulnerabilities by matching the package name, version, and repository ("https://rubygems.org/gems/"
).Beta Was this translation helpful? Give feedback.
All reactions