Skip to content

[Draft] Support Sarif POC#1110

Draft
tsim-sap wants to merge 2 commits intomainfrom
tsim-sap/issue-1059/support-sarif
Draft

[Draft] Support Sarif POC#1110
tsim-sap wants to merge 2 commits intomainfrom
tsim-sap/issue-1059/support-sarif

Conversation

@tsim-sap
Copy link
Collaborator

@tsim-sap tsim-sap commented Mar 4, 2026

Description

Please include a summary of the changes and the related issue. Please also include relevant motivation and context. List any dependencies that are required for this change.

What type of PR is this? (check all applicable)

  • 🍕 Feature
  • 🐛 Bug Fix
  • 📝 Documentation Update
  • 🎨 Style
  • 🧑‍💻 Code Refactor
  • 🔥 Performance Improvements
  • ✅ Test
  • 🤖 Build
  • 🔁 CI
  • 📦 Chore (Release)
  • ⏩ Revert

Related Tickets & Documents

  • Related Issue # (issue)
  • Closes # (issue)
  • Fixes # (issue)

Remove if not applicable

Added tests?

  • 👍 yes
  • 🙅 no, because they aren't needed
  • 🙋 no, because I need help
  • Separate ticket for tests # (issue/pr)

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

Added to documentation?

  • 📜 README.md
  • 🤝 Documentation pages updated
  • 🙅 no documentation needed
  • (if applicable) generated OpenAPI docs for CRD changes

Checklist

  • My code follows the style guidelines of this project
  • I have performed a self-review of my code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes

type ImportInput struct {
SARIFDocument string
ScannerName string
ServiceId int64
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this mean I import data only for the defined Service here?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah was thinking that would be a way to scope import to a selected service

artifactUri := parsedResult.ArtifactUri

// Resolve asset
// For POC, we mock the asset resolution
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the asset resolution is the crucial step that decides if we can import SARIF data easily or not. If I look at the example data:

          "properties": { "PkgName": "example/lib", "InstalledVersion": "1.0.0", "VulnerabilityID": "CVE-2024-58251" }

The properties key includes the component that is affected by the CVE. However, Heureka doesn't store this information, meaning a mapping to ComponentInstance is not possible.

Copy link
Collaborator

@michalkrzyz michalkrzyz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

seems good to me. Still I cannot imagine much how it is going to be integrated from the existing code. Let's see it.

@tsim-sap tsim-sap force-pushed the tsim-sap/issue-1059/support-sarif branch 2 times, most recently from 2cce21b to a06aabd Compare March 10, 2026 14:52
@tsim-sap tsim-sap force-pushed the tsim-sap/issue-1059/support-sarif branch from a06aabd to 9afd73a Compare March 16, 2026 13:45
@tsim-sap tsim-sap force-pushed the tsim-sap/issue-1059/support-sarif branch from 9afd73a to ab48bad Compare March 16, 2026 14:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants