feat: add tool annotations to GitLab security reports #2479
Conversation
This file contains hidden or 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
Extract and expose tool metadata from GitLab Security Reports using scanner field with fallback to analyzer. This enables consistent tool tracking across all material types (SARIF, SBOM, GitLab reports). Implementation uses scanner (actual security tool) as primary source and falls back to analyzer (wrapper) if scanner info is unavailable. Populates standard annotations: chainloop.material.tool.name and chainloop.material.tool.version. Resolves chainloop-dev#2478 Signed-off-by: Miguel Martinez <miguel@chainloop.dev>
Signed-off-by: Miguel Martinez <miguel@chainloop.dev>
javirln
approved these changes
Oct 24, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
Extract and expose tool metadata from GitLab Security Reports using scanner field with fallback to analyzer. This enables consistent tool tracking across all material types (SARIF, SBOM, GitLab reports).
Changes
gitlab.goto extract tool information fromscan.scanner(actual security tool) with fallback toscan.analyzer(wrapper/integration layer)injectAnnotationsmethod that populates standard annotations:chainloop.material.tool.nameandchainloop.material.tool.versionExamples
Resolves #2478