[Soner (shyim)]

Replace the Trivy container scan action with Docker Scout. Scan all 32 published PHP/version combinations from Docker Hub using the existing Docker Hub credentials and upload SARIF results to GitHub Code Scanning with stable per-image categories, including scans with zero findings.

Run nightly, on manual dispatch, and when .github/workflows/security.yml changes in a pull request or a push to main, so workflow failures are visible before merge. Remove the unused Dockerfile mappings and GHCR login. PR comments are disabled; job summaries remain enabled.

Validation: actionlint .github/workflows/security.yml and git diff --check passed. Docker Scout v1.27.0 was also run successfully against the four locally built PHP 8.4 ARM64 base/OTEL images.

Migration note: Scout is a separate code scanning tool. Existing Trivy alerts and analysis configurations are not automatically closed by Scout uploads and need to be retired separately.

[github-advanced-security]

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.