ci: security scanning, with the findings read and justified #5

Merged
marcos-mendez merged 1 commit from ci/security-scan into keel/trixie 2026-10-07 15:21:20 -03:00
marcos-mendez commented 2026-10-07 14:53:44 -03:00 (Migrated from github.com)

Calls security-scan.yml of keel-linux/.github (gitleaks, bandit,
semgrep, shellcheck on hosted runners, no secrets) on pull requests,
pushes to keel/trixie and by hand. Not a required check.

A scan of keel/trixie finds no secret in the history, no Python,
nothing for semgrep, and two shellcheck warnings in build.sh (SC2089,
SC2090): TEST_NGINX_GLOBALS carries literal quotes for the nginx test
harness, as intended. Justified in .github/security-baseline.

Calls security-scan.yml of keel-linux/.github (gitleaks, bandit, semgrep, shellcheck on hosted runners, no secrets) on pull requests, pushes to keel/trixie and by hand. Not a required check. A scan of keel/trixie finds no secret in the history, no Python, nothing for semgrep, and two shellcheck warnings in build.sh (SC2089, SC2090): TEST_NGINX_GLOBALS carries literal quotes for the nginx test harness, as intended. Justified in .github/security-baseline.
github-advanced-security[bot] commented 2026-10-07 14:57:52 -03:00 (Migrated from github.com)

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

  • The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
  • Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
  • You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool. ### What Enabling Code Scanning Means: - The 'Security' tab will display more code scanning analysis results (e.g., for the default branch). - Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. - You will be able to see the analysis results for the pull request's branch on this [overview](/Keel-Linux/libnginx-mod-http-coraza/security/code-scanning?query=pr%3A5+is%3Aopen) once the scans have completed and the checks have passed. For more information about GitHub Code Scanning, check out [the documentation](https://docs.github.com/code-security/code-scanning/introduction-to-code-scanning/about-code-scanning).
Sign in to join this conversation.
No description provided.