-
Couldn't load subscription status.
- Fork 727
Add for known bad CPE field combinations for jenkins package #405
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
Conversation
a6b630d to
00c3ab4
Compare
Benchmark Test ResultsBenchmark results from the latest changes vs base branch |
00c3ab4 to
ae55e5d
Compare
Signed-off-by: Alex Goodman <[email protected]>
ae55e5d to
18af21d
Compare
| // jira / atlassian should not apply to clients | ||
| if cpe.Vendor == "atlassian" && cpe.Product == "jira" && strings.Contains(p.Name, "client") { | ||
| return true | ||
| if cpe.Product == "jira" && strings.Contains(strings.ToLower(p.Name), "client") { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: Now that we're amassing some nontrivial, specialized rules in our list of filterFn, it would be nice to codify these as named functions that get referenced here in this list. But I'm making this a "nit" due to the context of our CPE implementation future
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
agreed with the long term approach, and held off for similar considerations 👍
Add for known bad CPE field combinations for jenkins package
This adds a filter to eliminate guesses that would result in matching jenkins server without having a package name that minimally reflects this.
Additionally updates the jira filter to consider
wfn.Anyvendor values.