Skip to content
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
merged 2 commits into from
Dec 13, 2023

Conversation

srmish-jfrog
Copy link
Contributor

…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.

  • [v] All tests passed. If this feature is not already covered by the tests, I added new tests.
  • [v] I used npm run format for formatting the code before submitting the pull request.

@Or-Geva 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 github-actions bot removed the safe to test Approve running integration tests on a pull request label Nov 27, 2023
@srmish-jfrog srmish-jfrog force-pushed the applicability_indirect_cves branch from a689bde to 6c2cce6 Compare November 27, 2023 20:23
@srmish-jfrog srmish-jfrog force-pushed the applicability_indirect_cves branch from 6c2cce6 to 575e735 Compare November 27, 2023 21:04
@Or-Geva Or-Geva added the safe to test Approve running integration tests on a pull request label Nov 28, 2023
@Or-Geva Or-Geva self-requested a review November 28, 2023 07:35
@github-actions github-actions bot removed the safe to test Approve running integration tests on a pull request label Nov 28, 2023
Copy link
Contributor

👍 Frogbot scanned this pull request and found that it did not add vulnerable dependencies.


@srmish-jfrog srmish-jfrog force-pushed the applicability_indirect_cves branch from bb04bcc to 62d7009 Compare December 1, 2023 18:55
@Or-Geva Or-Geva added the safe to test Approve running integration tests on a pull request label Dec 2, 2023
@github-actions github-actions bot removed the safe to test Approve running integration tests on a pull request label Dec 2, 2023
@srmish-jfrog srmish-jfrog force-pushed the applicability_indirect_cves branch from 62d7009 to 6e3ab88 Compare December 2, 2023 08:32
@Or-Geva Or-Geva added the safe to test Approve running integration tests on a pull request label Dec 3, 2023
@github-actions github-actions bot removed the safe to test Approve running integration tests on a pull request label Dec 3, 2023
@Or-Geva Or-Geva added the safe to test Approve running integration tests on a pull request label Dec 10, 2023
@github-actions github-actions bot removed the safe to test Approve running integration tests on a pull request label Dec 10, 2023
@Or-Geva Or-Geva added the safe to test Approve running integration tests on a pull request label Dec 13, 2023
@github-actions 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.
@Or-Geva Or-Geva added the safe to test Approve running integration tests on a pull request label Dec 13, 2023
@github-actions github-actions bot removed the safe to test Approve running integration tests on a pull request label Dec 13, 2023
@Or-Geva Or-Geva merged commit 1a9ae97 into jfrog:master Dec 13, 2023
9 of 10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
improvement Automatically generated release notes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants