-
Notifications
You must be signed in to change notification settings - Fork 35
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
applicabilityScan: add "indirect-cve-whitelist" to scanner YAML confi… #450
Merged
Or-Geva
merged 2 commits into
jfrog:master
from
srmish-jfrog:applicability_indirect_cves
Dec 13, 2023
Merged
applicabilityScan: add "indirect-cve-whitelist" to scanner YAML confi… #450
Or-Geva
merged 2 commits into
jfrog:master
from
srmish-jfrog:applicability_indirect_cves
Dec 13, 2023
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Or-Geva
added
improvement
Automatically generated release notes
safe to test
Approve running integration tests on a pull request
labels
Nov 27, 2023
github-actions
bot
removed
the
safe to test
Approve running integration tests on a pull request
label
Nov 27, 2023
srmish-jfrog
force-pushed
the
applicability_indirect_cves
branch
from
November 27, 2023 20:23
a689bde
to
6c2cce6
Compare
srmish-jfrog
had a problem deploying
to
frogbot
November 27, 2023 20:23 — with
GitHub Actions
Failure
srmish-jfrog
force-pushed
the
applicability_indirect_cves
branch
from
November 27, 2023 21:04
6c2cce6
to
575e735
Compare
Or-Geva
added
the
safe to test
Approve running integration tests on a pull request
label
Nov 28, 2023
github-actions
bot
removed
the
safe to test
Approve running integration tests on a pull request
label
Nov 28, 2023
Or-Geva
suggested changes
Nov 29, 2023
srmish-jfrog
had a problem deploying
to
frogbot
December 1, 2023 18:54 — with
GitHub Actions
Failure
srmish-jfrog
force-pushed
the
applicability_indirect_cves
branch
from
December 1, 2023 18:55
bb04bcc
to
62d7009
Compare
srmish-jfrog
had a problem deploying
to
frogbot
December 1, 2023 18:55 — with
GitHub Actions
Failure
Or-Geva
added
the
safe to test
Approve running integration tests on a pull request
label
Dec 2, 2023
github-actions
bot
removed
the
safe to test
Approve running integration tests on a pull request
label
Dec 2, 2023
srmish-jfrog
force-pushed
the
applicability_indirect_cves
branch
from
December 2, 2023 08:32
62d7009
to
6e3ab88
Compare
srmish-jfrog
had a problem deploying
to
frogbot
December 2, 2023 08:32 — with
GitHub Actions
Failure
Or-Geva
added
the
safe to test
Approve running integration tests on a pull request
label
Dec 3, 2023
github-actions
bot
removed
the
safe to test
Approve running integration tests on a pull request
label
Dec 3, 2023
Or-Geva
added
the
safe to test
Approve running integration tests on a pull request
label
Dec 10, 2023
github-actions
bot
removed
the
safe to test
Approve running integration tests on a pull request
label
Dec 10, 2023
Or-Geva
added
the
safe to test
Approve running integration tests on a pull request
label
Dec 13, 2023
github-actions
bot
removed
the
safe to test
Approve running integration tests on a pull request
label
Dec 13, 2023
…guration Add support for applicability scanning of indirect (transitive) CVEs. This is done by sending a separate list of detected indirect CVEs (indirect-cve-whitelist) to the applicability scanner YAML configuration file.
srmish-jfrog
force-pushed
the
applicability_indirect_cves
branch
from
December 13, 2023 07:40
6e3ab88
to
30e8e44
Compare
srmish-jfrog
had a problem deploying
to
frogbot
December 13, 2023 07:40 — with
GitHub Actions
Failure
Or-Geva
added
the
safe to test
Approve running integration tests on a pull request
label
Dec 13, 2023
github-actions
bot
removed
the
safe to test
Approve running integration tests on a pull request
label
Dec 13, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…guration
Add support for applicability scanning of indirect (transitive) CVEs. This is done by sending a separate list of detected indirect CVEs (indirect-cve-whitelist) to the applicability scanner YAML configuration file.
npm run format
for formatting the code before submitting the pull request.