Init NormalizeByCVE to true

[dwertent]

type:

enhancement

---

description:

This PR introduces a change in the GrypeAdapter's vulnerability matcher configuration. Specifically, it sets the 'NormalizeByCVE' attribute to true. This change will ensure that the vulnerabilities are normalized by their CVE identifiers, providing a more standardized and consistent output.

---

main_files_walkthrough:

files:

- `adapters/v1/grype.go`: The 'NormalizeByCVE' attribute of the 'VulnerabilityMatcher' in the 'ScanSBOM' function is now set to true.

---

User Description:

Overview

cc @slashben

[codiumai-pr-agent[bot]]

PR Description updated to latest commit (https://github.com/kubescape/kubevuln/commit/48a5a23a147ecfee366a0a4865a3ef133d7d65df)

[codiumai-pr-agent[bot]]

PR Analysis

• 🎯 Main theme: Enhancing the GrypeAdapter's vulnerability matcher configuration

• 📝 PR summary: This PR modifies the GrypeAdapter's vulnerability matcher configuration in the 'ScanSBOM' function by setting the 'NormalizeByCVE' attribute to true. This change aims to normalize vulnerabilities by their CVE identifiers, providing a more standardized and consistent output.

• 📌 Type of PR: Enhancement

• 🧪 Relevant tests added: No

• ⏱️ Estimated effort to review [1-5]: 1, because the PR involves a simple and straightforward change in a single line of code.

• 🔒 Security concerns: No security concerns found

  PR Feedback

• 💡 General suggestions: It would be beneficial to include tests that verify the new behavior introduced by setting 'NormalizeByCVE' to true. This will ensure that the change works as expected and does not introduce any regressions.

• 🤖 Code feedback:

  - **relevant file:** ``adapters/v1/grype.go`` **suggestion:** Consider adding error handling for the case when the 'NormalizeByCVE' attribute fails to set to true. This will ensure that any issues are caught and handled appropriately. [important] **relevant line:** [NormalizeByCVE: true,](https://github.com/kubescape/kubevuln/pull/189/files#diff-665c620467429b3c5376c54c77dfbc3fd78f7f5cda60b1c53cc36fd0b1a9f39eR142)

How to use

Instructions

> To invoke the PR-Agent, add a comment using one of the following commands: > **/review**: Request a review of your Pull Request. > **/describe**: Update the PR title and description based on the contents of the PR. > **/improve [--extended]**: Suggest code improvements. Extended mode provides a higher quality feedback. > **/ask \**: Ask a question about the PR. > **/update_changelog**: Update the changelog based on the PR's contents. > **/add_docs**: Generate docstring for new components introduced in the PR. > **/generate_labels**: Generate labels for the PR based on the PR's contents. > see the [tools guide](https://github.com/Codium-ai/pr-agent/blob/main/docs/TOOLS_GUIDE.md) for more details. >To edit any configuration parameter from the [configuration.toml](https://github.com/Codium-ai/pr-agent/blob/main/pr_agent/settings/configuration.toml), add --config_path=new_value. >For example: /review --pr_reviewer.extra_instructions="focus on the file: ..." >To list the possible configuration parameters, add a **/config** comment.

[github-actions[bot]]

Summary:

• License scan: failure
• Credentials scan: success
• Vulnerabilities scan: success
• Unit test: success
• Go linting: success

[dwertent]

I included this code in #196