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

Closed

marcos-mendez wants to merge 1 commit from ci/security-scan into main

marcos-mendez commented

2026-10-07 14:57:05 -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 main and by hand. Not a required check.

A scan of main finds no secret in the history and no shellcheck
finding. semgrep's phpinfo-use (ERROR) on overlay/var/www/phpinfo.php is
left out of the baseline on purpose: the page publishes the PHP
configuration to anyone on port 80, which is a real disclosure, so the
semgrep check stays red until the project decides whether an appliance
ships it.

Calls security-scan.yml of keel-linux/.github (gitleaks, bandit, semgrep, shellcheck on hosted runners, no secrets) on pull requests, pushes to main and by hand. Not a required check. A scan of main finds no secret in the history and no shellcheck finding. semgrep's phpinfo-use (ERROR) on overlay/var/www/phpinfo.php is left out of the baseline on purpose: the page publishes the PHP configuration to anyone on port 80, which is a real disclosure, so the semgrep check stays red until the project decides whether an appliance ships it.

github-advanced-security[bot] commented

2026-10-07 15:03:44 -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/keel-apache-php/security/code-scanning?query=pr%3A6+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).

marcos-mendez commented

2026-10-07 15:39:15 -03:00

(Migrated from github.com)

Closing: Apache is retired in Keel (LEMP with nginx and php-fpm replaces LAMP/LAPP, decisions 0023-0040); this repository is being archived.

Commenting is not possible because the repository is archived.

No reviewers