Replies: 5 comments 1 reply
|
Created https://issues.redhat.com/browse/PROJQUAY-5100 to track this request. |
0 replies
|
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? |
1 reply
|
Okay, I refuse to re-inflict the braindamage of reading |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
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
nameandversion, 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/").All reactions