ci: add semgrep check #220
Open
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
ali-ince
approved these changes
Jan 8, 2026
Contributor
ali-ince
left a comment
ali-ince
left a comment
There was a problem hiding this comment.
This is good to go, I think we should work on nightly builds to cover both for 5, 5-dev, 2025, and 2025-dev as we do with spark & kafka as a separate step.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR adds a Semgrep check to CI pipeline. Linear card
Key changes:
Introduce a separate build to generate maven dependency tree and perform Semgrep scan. Scan results are integrated with Semgrep UI and available in the scan history.
Scans are performed on each pull request, main branch. Added a nightly build with semgrep only.
Note: --no-git-ignore file apparently required to both discover language rules and scan tree files correctly.
The change wasn't tested yet.