Semgrep in CI vs CLI: align your SAST scan results and understand differences
How to align your scan results between CI and CLI and understand differences in behavior.
How to align your scan results between CI and CLI and understand differences in behavior.
Learn how to set up reusable GitHub workflows for Semgrep scans.
To prevent duplicated findings, perform full scans only on the main branch of your repository.
To prevent "resource not accessible by integration" error when running job to upload findings to GitHub's Advanced Security Dashboard
When Semgrep comments on PR or MR findings, the comments are usually posted on the line of code where the finding is identified (inline). However, there are two common reasons why comments may not appear inline.
Use this reference to check why you may not be receiving Semgrep comments on PRs or MRs.