ci: add reusable SAST workflow, remove SonarQube - #2
Closed
cwilliams-security wants to merge 2 commits into
Closed
Conversation
cwilliams-security
changed the title
Author
|
Closing — this repo is no longer actively maintained. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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
security-scan.yml— a thin caller delegating tointellum/intellum-security/.github/workflows/sast-reusable.yml@sast-prod(Semgrep + TruffleHog + Trivy)sonarqube-check.yml— Semgrep in the reusable pipeline covers the same SAST surface, making SonarQube redundantWhy
Part of SEC-2656 — centralizing SAST scanning across Intellum repos and consolidating tooling. One place to update tool versions, rules, and scan logic; no more per-repo drift.
Test plan
sonarqube-check.ymlno longer appears in Actions after merge🤖 Opened by cwilliams-security via SEC-2656