x-scan-container-security

To scan a Docker image for vulnerabilities and generate a SARIF report, run the skill to identify CVEs, apply severity thresholds, and output SARIF 2.1.0 data alongside a Markdown report. It uses Trivy, Grype, or Snyk Container based on availability.

Yes, you can lint a Dockerfile for security best-practice violations alongside container image scanning. The skill analyzes Dockerfiles, identifies known CVEs in images, and unifies the results into a single SARIF 2.1.0 report with severity scoring.

Yes, this container security scanner supports Trivy, Grype, and Snyk Container. It features automatic tool selection based on which scanner is available in your environment to perform combined image and Dockerfile security scanning.

The best way to integrate Docker image vulnerability scanning into a CI/CD pipeline is using severity-aware filtering with SARIF report generation. This skill outputs SARIF 2.1.0 data to streamline security workflows and grade assignments in automated deployments.

You need SARIF output for container security scanning when integrating vulnerability results into CI/CD pipelines or developer workflows that require standardized reporting. The skill produces SARIF 2.1.0 data with severity scoring to streamline these security workflows.

When scanning Docker images, the skill relies on having Trivy, Grype, or Snyk Container available in the environment. It features automatic tool selection based on availability, so scanning cannot proceed if none of these supported tools are installed.