-
Notifications
You must be signed in to change notification settings - Fork 4
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
fix(sdk): fix critical/high vulenerabilities #6
Conversation
Library Vulnerability scan resultsThe following vulnerabilities have been found in libraries included in the repository (some might be dependencies of dependencies). Critical 🔴 and High 🟡 severity vulnerabilities must be fixed before the PR can be merged, even if they are dependencies of dependencies.
|
Library Vulnerability scan resultsThe following vulnerabilities have been found in libraries included in the repository (some might be dependencies of dependencies). Critical 🔴 and High 🟡 severity vulnerabilities must be fixed before the PR can be merged, even if they are dependencies of dependencies.
|
Library Vulnerability scan resultsThe following vulnerabilities have been found in libraries included in the repository (some might be dependencies of dependencies). Critical 🔴 and High 🟡 severity vulnerabilities must be fixed before the PR can be merged, even if they are dependencies of dependencies.
|
Library Vulnerability scan resultsThe following vulnerabilities have been found in libraries included in the repository (some might be dependencies of dependencies). Critical 🔴 and High 🟡 severity vulnerabilities must be fixed before the PR can be merged, even if they are dependencies of dependencies.
|
Library Vulnerability scan resultsThe following vulnerabilities have been found in libraries included in the repository (some might be dependencies of dependencies). Critical 🔴 and High 🟡 severity vulnerabilities must be fixed before the PR can be merged, even if they are dependencies of dependencies.
|
Quality Gate passedIssues Measures |
The CI/unit-test failed is not caused by the patch, it's existing issue, will be fixed in #5 |
* feat: KRAKEN-74 * fix: change ui * feat: read file * fix: read yaml file * feat: integrate api and list * feat: API list view children * feat: config unit test --------- Co-authored-by: Tim Pham <[email protected]>
Description
The CI reported a couple of cirtical/high vulnerabilities, looks like the root cause is the CI tool can't detect the maven packages used by the project ( vulnerable version is empty), config the version in the pom.xml for the dependencies should be able to fix this issue.
Types of changes
Checklist