[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AB6RM3BC0R2X9VQ1D01RTS":3,"skill-same:01M7AB6RM3BC0R2X9VQ1D01RTS":102},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":47,"commitSha":48,"skillDirectory":49,"forksCount":14,"repositoryHtmlUrl":50,"repositoryHomepageUrl":6,"ownerHtmlUrl":51,"ownerBlogUrl":6,"ownerDescription":52,"updatedAt":53,"install":54,"resources":67},"01M7AB6RM3BC0R2X9VQ1D01RTS","scanning-containers-with-trivy-in-cicd",null,"Integrates Aqua Security's Trivy scanner into CI\u002FCD pipelines to detect OS package and application dependency CVEs, Dockerfile misconfigurations, and issues in filesystems or git repositories, and to enforce severity-based quality gates that block vulnerable images from being deployed. Use when building Docker images in CI\u002FCD and needing automated vulnerability scanning and pass\u002Ffail gates before registry push or production deployment.","NeelakshSaxena\u002FVayu","NeelakshSaxena","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F87892838?v=4","01M7A3B9YFS6F6N9DD1787DT86","Neelaksh Saxena","01M7A3B9ZKBT09MNMPX2XN69BY",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fscanning-containers-with-trivy-in-cicd\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fscanning-containers-with-trivy-in-cicd\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: scanning-containers-with-trivy-in-cicd\ndescription: 'Integrates Aqua Security''s Trivy scanner into CI\u002FCD pipelines to detect\n  OS package and application dependency CVEs, Dockerfile misconfigurations, and issues\n  in filesystems or git repositories, and to enforce severity-based quality gates that\n  block vulnerable images from being deployed. Use when building Docker images in\n  CI\u002FCD and needing automated vulnerability scanning and pass\u002Ffail gates before registry\n  push or production deployment.\n\n  '\ndomain: cybersecurity\nsubdomain: devsecops\ntags:\n- devsecops\n- cicd\n- trivy\n- container-security\n- vulnerability-scanning\n- secure-sdlc\nversion: 1.0.0\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- PR.PS-01\n- GV.SC-07\n- ID.IM-04\n- PR.PS-04\nmitre_attack:\n- T1195\n- T1554\n- T1059.004\n- T1610\n- T1611\n---\n\n# Scanning Containers with Trivy in CI\u002FCD\n\n## When to Use\n\n- When building Docker container images in CI\u002FCD and needing automated vulnerability scanning before registry push\n- When establishing quality gates that prevent images with critical or high CVEs from reaching production\n- When compliance requirements mandate vulnerability scanning of all container images before deployment\n- When scanning IaC files (Dockerfiles, Kubernetes manifests) alongside container image scanning\n- When needing a single tool to scan OS packages, language-specific dependencies, and misconfigurations\n\n**Do not use** for runtime container security monitoring (use Falco), for scanning running containers in production (use runtime agents), or when only scanning application source code without containerization (use SAST tools).\n\n## Prerequisites\n\n- Trivy CLI installed (v0.50+) or access to aquasecurity\u002Ftrivy-action GitHub Action\n- Docker daemon available in CI\u002FCD for building and scanning images\n- Container registry credentials for pulling base images and pushing scanned images\n- Trivy vulnerability database accessible (downloaded automatically or cached)\n\n## Workflow\n\n### Step 1: Configure Trivy Scanning in GitHub Actions\n\nSet up a GitHub Actions workflow that builds a Docker image and scans it with Trivy before pushing to a container registry.\n\n```yaml\n# .github\u002Fworkflows\u002Fcontainer-security.yml\nname: Container Security Scan\n\non:\n  push:\n    branches: [main]\n  pull_request:\n    branches: [main]\n    paths:\n      - 'Dockerfile'\n      - 'docker-compose*.yml'\n      - 'src\u002F**'\n      - 'requirements*.txt'\n      - 'package*.json'\n\njobs:\n  build-and-scan:\n    runs-on: ubuntu-latest\n    permissions:\n      security-events: write\n      contents: read\n\n    steps:\n      - uses: actions\u002Fcheckout@v4\n\n      - name: Build Docker image\n        run: docker build -t app:${{ github.sha }} .\n\n      - name: Run Trivy vulnerability scanner\n        uses: aquasecurity\u002Ftrivy-action@0.28.0\n        with:\n          image-ref: 'app:${{ github.sha }}'\n          format: 'sarif'\n          output: 'trivy-results.sarif'\n          severity: 'CRITICAL,HIGH'\n          exit-code: '1'\n          ignore-unfixed: true\n\n      - name: Upload Trivy scan results\n        uses: github\u002Fcodeql-action\u002Fupload-sarif@v3\n        if: always()\n        with:\n          sarif_file: 'trivy-results.sarif'\n          category: 'trivy-container'\n\n      - name: Run Trivy misconfiguration scanner\n        uses: aquasecurity\u002Ftrivy-action@0.28.0\n        with:\n          scan-type: 'config'\n          scan-ref: '.'\n          format: 'table'\n          exit-code: '1'\n          severity: 'CRITICAL,HIGH'\n```\n\n### Step 2: Scan Dockerfiles for Misconfigurations\n\nTrivy detects common Dockerfile security issues such as running as root, using latest tags, and exposing unnecessary ports.\n\n```bash\n# Scan Dockerfile for misconfigurations\ntrivy config --severity HIGH,CRITICAL .\u002FDockerfile\n\n# Scan with custom policy directory\ntrivy config --policy .\u002Fsecurity-policies --severity MEDIUM,HIGH,CRITICAL .\n\n# Example secure Dockerfile practices Trivy checks for:\n# - USER instruction present (not running as root)\n# - HEALTHCHECK instruction defined\n# - Base image uses specific tag, not :latest\n# - No secrets in ENV or ARG instructions\n# - COPY preferred over ADD\n```\n\n### Step 3: Integrate with GitLab CI\u002FCD\n\n```yaml\n# .gitlab-ci.yml\nstages:\n  - build\n  - scan\n  - push\n\nvariables:\n  TRIVY_CACHE_DIR: .trivycache\u002F\n\nbuild:\n  stage: build\n  script:\n    - docker build -t $CI_REGISTRY_IMAGE:$CI_COMMIT_SHA .\n    - docker save $CI_REGISTRY_IMAGE:$CI_COMMIT_SHA -o image.tar\n  artifacts:\n    paths:\n      - image.tar\n\ntrivy-scan:\n  stage: scan\n  image:\n    name: aquasec\u002Ftrivy:latest\n    entrypoint: [\"\"]\n  cache:\n    paths:\n      - .trivycache\u002F\n  script:\n    - trivy image\n        --input image.tar\n        --exit-code 1\n        --severity CRITICAL,HIGH\n        --ignore-unfixed\n        --format json\n        --output trivy-report.json\n    - trivy image\n        --input image.tar\n        --severity CRITICAL,HIGH,MEDIUM\n        --format table\n  artifacts:\n    reports:\n      container_scanning: trivy-report.json\n    paths:\n      - trivy-report.json\n  allow_failure: false\n\npush:\n  stage: push\n  needs: [trivy-scan]\n  script:\n    - docker load -i image.tar\n    - docker push $CI_REGISTRY_IMAGE:$CI_COMMIT_SHA\n```\n\n### Step 4: Configure Trivy Ignore and Exception Handling\n\nManage false positives and accepted risks through Trivy's ignore file and VEX statements.\n\n```yaml\n# .trivyignore.yaml\nvulnerabilities:\n  - id: CVE-2023-44487    # HTTP\u002F2 rapid reset - mitigated at load balancer\n    statement: \"Mitigated by WAF rate limiting at ingress layer\"\n    expires: 2026-06-01\n\n  - id: CVE-2024-21626    # runc container escape - patched in base image update\n    statement: \"Tracked in JIRA-SEC-1234, base image update scheduled\"\n    expires: 2026-03-15\n\nmisconfigurations:\n  - id: DS002             # User not set - required for init containers\n    paths:\n      - \"docker\u002Finit-container\u002FDockerfile\"\n    statement: \"Init container requires root for volume permission setup\"\n```\n\n### Step 5: Implement Database Caching and Offline Scanning\n\nCache the Trivy vulnerability database in CI\u002FCD to reduce scan times and enable air-gapped environments.\n\n```yaml\n# GitHub Actions with database caching\n- name: Cache Trivy DB\n  uses: actions\u002Fcache@v4\n  with:\n    path: \u002Ftmp\u002Ftrivy-db\n    key: trivy-db-${{ hashFiles('.github\u002Fworkflows\u002Fcontainer-security.yml') }}\n    restore-keys: trivy-db-\n\n- name: Run Trivy with cached DB\n  uses: aquasecurity\u002Ftrivy-action@0.28.0\n  with:\n    image-ref: 'app:${{ github.sha }}'\n    cache-dir: \u002Ftmp\u002Ftrivy-db\n    format: 'json'\n    output: 'trivy-results.json'\n    severity: 'CRITICAL,HIGH'\n    exit-code: '1'\n```\n\n```bash\n# Air-gapped: Download DB manually and mount\ntrivy image --download-db-only --cache-dir \u002Fpath\u002Fto\u002Fcache\n# Transfer cache to air-gapped system\ntrivy image --skip-db-update --cache-dir \u002Fpath\u002Fto\u002Fcache myimage:tag\n```\n\n### Step 6: Generate SBOM and Scan for License Compliance\n\nUse Trivy to generate Software Bill of Materials alongside vulnerability scanning.\n\n```bash\n# Generate SBOM in CycloneDX format\ntrivy image --format cyclonedx --output sbom.cdx.json app:latest\n\n# Generate SBOM in SPDX format\ntrivy image --format spdx-json --output sbom.spdx.json app:latest\n\n# Scan SBOM for vulnerabilities (decouple generation from scanning)\ntrivy sbom sbom.cdx.json --severity CRITICAL,HIGH\n\n# Scan with license detection\ntrivy image --scanners vuln,license --severity HIGH,CRITICAL app:latest\n```\n\n## Key Concepts\n\n| Term | Definition |\n|------|------------|\n| CVE | Common Vulnerabilities and Exposures — standardized identifiers for publicly known security vulnerabilities |\n| Vulnerability DB | Trivy's regularly updated database aggregating CVE data from NVD, vendor advisories, and language-specific sources |\n| Misconfiguration | Security-relevant configuration issue in Dockerfiles, Kubernetes manifests, or IaC templates |\n| SBOM | Software Bill of Materials — complete inventory of all components and dependencies in a container image |\n| Ignore Unfixed | Flag to skip CVEs without available patches, reducing noise from vulnerabilities with no actionable fix |\n| VEX | Vulnerability Exploitability eXchange — machine-readable statements about whether a vulnerability is exploitable in context |\n| Exit Code | Non-zero return code from Trivy when findings exceed the severity threshold, used to fail CI\u002FCD pipelines |\n\n## Tools & Systems\n\n- **Trivy**: Open-source vulnerability scanner by Aqua Security supporting images, filesystems, repos, and IaC\n- **trivy-action**: Official GitHub Action for running Trivy scans in GitHub Actions workflows\n- **Trivy Operator**: Kubernetes operator that continuously scans cluster workloads with Trivy\n- **Grype**: Alternative image scanner by Anchore for comparison and validation of scan results\n- **Harbor**: Container registry with built-in Trivy integration for automatic image scanning on push\n\n## Common Scenarios\n\n### Scenario: Multi-Stage Build with Separate Scan and Push\n\n**Context**: A team builds multi-stage Docker images and needs to scan the final production image before pushing to ECR, while also scanning the build stage for supply chain risks.\n\n**Approach**:\n1. Build the Docker image with `--target production` for the final stage\n2. Run Trivy with `--severity CRITICAL,HIGH --exit-code 1 --ignore-unfixed` to block on exploitable issues\n3. Generate an SBOM in CycloneDX format and store as a build artifact\n4. Upload SARIF results to GitHub Security tab for visibility\n5. Only push to ECR if the Trivy scan exits with code 0\n6. Tag the pushed image with the scan timestamp and Trivy DB version for audit traceability\n\n**Pitfalls**: Scanning only the final stage misses vulnerable packages that were present in build stages and may have influenced the build. Run `trivy fs` on the build context separately. Caching the Trivy DB too aggressively (weekly) means newly published CVEs take days to appear in scans.\n\n## Output Format\n\n```\nTrivy Container Scan Report\n=============================\nImage: app:a1b2c3d4\nBase Image: python:3.12-slim-bookworm\nScan Date: 2026-02-23\nDB Version: 2026-02-23T00:15:00Z\n\nVULNERABILITY SUMMARY:\n  Total: 47\n  Critical: 2\n  High: 5\n  Medium: 18\n  Low: 22\n  Unfixed: 8 (excluded from gate)\n\nCRITICAL FINDINGS:\n  CVE-2025-12345  libssl3    3.0.11-1  3.0.13-1  OpenSSL buffer overflow\n  CVE-2025-67890  curl       7.88.1-10 7.88.1-12 curl HSTS bypass\n\nHIGH FINDINGS:\n  CVE-2025-11111  zlib1g     1.2.13    1.2.13.1  zlib heap buffer overflow\n  CVE-2025-22222  python3.12 3.12.1    3.12.3    CPython path traversal\n  CVE-2025-33333  requests   2.31.0    2.32.0    requests SSRF in redirects\n\nMISCONFIGURATION:\n  DS002  [HIGH]   Dockerfile: USER instruction not set (running as root)\n  DS026  [MEDIUM] Dockerfile: No HEALTHCHECK defined\n\nQUALITY GATE: FAILED (2 Critical, 5 High findings)\n```\n","# Scanning Containers with Trivy in CI\u002FCD\n\n## When to Use\n\n- When building Docker container images in CI\u002FCD and needing automated vulnerability scanning before registry push\n- When establishing quality gates that prevent images with critical or high CVEs from reaching production\n- When compliance requirements mandate vulnerability scanning of all container images before deployment\n- When scanning IaC files (Dockerfiles, Kubernetes manifests) alongside container image scanning\n- When needing a single tool to scan OS packages, language-specific dependencies, and misconfigurations\n\n**Do not use** for runtime container security monitoring (use Falco), for scanning running containers in production (use runtime agents), or when only scanning application source code without containerization (use SAST tools).\n\n## Prerequisites\n\n- Trivy CLI installed (v0.50+) or access to aquasecurity\u002Ftrivy-action GitHub Action\n- Docker daemon available in CI\u002FCD for building and scanning images\n- Container registry credentials for pulling base images and pushing scanned images\n- Trivy vulnerability database accessible (downloaded automatically or cached)\n\n## Workflow\n\n### Step 1: Configure Trivy Scanning in GitHub Actions\n\nSet up a GitHub Actions workflow that builds a Docker image and scans it with Trivy before pushing to a container registry.\n\n```yaml\n# .github\u002Fworkflows\u002Fcontainer-security.yml\nname: Container Security Scan\n\non:\n  push:\n    branches: [main]\n  pull_request:\n    branches: [main]\n    paths:\n      - 'Dockerfile'\n      - 'docker-compose*.yml'\n      - 'src\u002F**'\n      - 'requirements*.txt'\n      - 'package*.json'\n\njobs:\n  build-and-scan:\n    runs-on: ubuntu-latest\n    permissions:\n      security-events: write\n      contents: read\n\n    steps:\n      - uses: actions\u002Fcheckout@v4\n\n      - name: Build Docker image\n        run: docker build -t app:${{ github.sha }} .\n\n      - name: Run Trivy vulnerability scanner\n        uses: aquasecurity\u002Ftrivy-action@0.28.0\n        with:\n          image-ref: 'app:${{ github.sha }}'\n          format: 'sarif'\n          output: 'trivy-results.sarif'\n          severity: 'CRITICAL,HIGH'\n          exit-code: '1'\n          ignore-unfixed: true\n\n      - name: Upload Trivy scan results\n        uses: github\u002Fcodeql-action\u002Fupload-sarif@v3\n        if: always()\n        with:\n          sarif_file: 'trivy-results.sarif'\n          category: 'trivy-container'\n\n      - name: Run Trivy misconfiguration scanner\n        uses: aquasecurity\u002Ftrivy-action@0.28.0\n        with:\n          scan-type: 'config'\n          scan-ref: '.'\n          format: 'table'\n          exit-code: '1'\n          severity: 'CRITICAL,HIGH'\n```\n\n### Step 2: Scan Dockerfiles for Misconfigurations\n\nTrivy detects common Dockerfile security issues such as running as root, using latest tags, and exposing unnecessary ports.\n\n```bash\n# Scan Dockerfile for misconfigurations\ntrivy config --severity HIGH,CRITICAL .\u002FDockerfile\n\n# Scan with custom policy directory\ntrivy config --policy .\u002Fsecurity-policies --severity MEDIUM,HIGH,CRITICAL .\n\n# Example secure Dockerfile practices Trivy checks for:\n# - USER instruction present (not running as root)\n# - HEALTHCHECK instruction defined\n# - Base image uses specific tag, not :latest\n# - No secrets in ENV or ARG instructions\n# - COPY preferred over ADD\n```\n\n### Step 3: Integrate with GitLab CI\u002FCD\n\n```yaml\n# .gitlab-ci.yml\nstages:\n  - build\n  - scan\n  - push\n\nvariables:\n  TRIVY_CACHE_DIR: .trivycache\u002F\n\nbuild:\n  stage: build\n  script:\n    - docker build -t $CI_REGISTRY_IMAGE:$CI_COMMIT_SHA .\n    - docker save $CI_REGISTRY_IMAGE:$CI_COMMIT_SHA -o image.tar\n  artifacts:\n    paths:\n      - image.tar\n\ntrivy-scan:\n  stage: scan\n  image:\n    name: aquasec\u002Ftrivy:latest\n    entrypoint: [\"\"]\n  cache:\n    paths:\n      - .trivycache\u002F\n  script:\n    - trivy image\n        --input image.tar\n        --exit-code 1\n        --severity CRITICAL,HIGH\n        --ignore-unfixed\n        --format json\n        --output trivy-report.json\n    - trivy image\n        --input image.tar\n        --severity CRITICAL,HIGH,MEDIUM\n        --format table\n  artifacts:\n    reports:\n      container_scanning: trivy-report.json\n    paths:\n      - trivy-report.json\n  allow_failure: false\n\npush:\n  stage: push\n  needs: [trivy-scan]\n  script:\n    - docker load -i image.tar\n    - docker push $CI_REGISTRY_IMAGE:$CI_COMMIT_SHA\n```\n\n### Step 4: Configure Trivy Ignore and Exception Handling\n\nManage false positives and accepted risks through Trivy's ignore file and VEX statements.\n\n```yaml\n# .trivyignore.yaml\nvulnerabilities:\n  - id: CVE-2023-44487    # HTTP\u002F2 rapid reset - mitigated at load balancer\n    statement: \"Mitigated by WAF rate limiting at ingress layer\"\n    expires: 2026-06-01\n\n  - id: CVE-2024-21626    # runc container escape - patched in base image update\n    statement: \"Tracked in JIRA-SEC-1234, base image update scheduled\"\n    expires: 2026-03-15\n\nmisconfigurations:\n  - id: DS002             # User not set - required for init containers\n    paths:\n      - \"docker\u002Finit-container\u002FDockerfile\"\n    statement: \"Init container requires root for volume permission setup\"\n```\n\n### Step 5: Implement Database Caching and Offline Scanning\n\nCache the Trivy vulnerability database in CI\u002FCD to reduce scan times and enable air-gapped environments.\n\n```yaml\n# GitHub Actions with database caching\n- name: Cache Trivy DB\n  uses: actions\u002Fcache@v4\n  with:\n    path: \u002Ftmp\u002Ftrivy-db\n    key: trivy-db-${{ hashFiles('.github\u002Fworkflows\u002Fcontainer-security.yml') }}\n    restore-keys: trivy-db-\n\n- name: Run Trivy with cached DB\n  uses: aquasecurity\u002Ftrivy-action@0.28.0\n  with:\n    image-ref: 'app:${{ github.sha }}'\n    cache-dir: \u002Ftmp\u002Ftrivy-db\n    format: 'json'\n    output: 'trivy-results.json'\n    severity: 'CRITICAL,HIGH'\n    exit-code: '1'\n```\n\n```bash\n# Air-gapped: Download DB manually and mount\ntrivy image --download-db-only --cache-dir \u002Fpath\u002Fto\u002Fcache\n# Transfer cache to air-gapped system\ntrivy image --skip-db-update --cache-dir \u002Fpath\u002Fto\u002Fcache myimage:tag\n```\n\n### Step 6: Generate SBOM and Scan for License Compliance\n\nUse Trivy to generate Software Bill of Materials alongside vulnerability scanning.\n\n```bash\n# Generate SBOM in CycloneDX format\ntrivy image --format cyclonedx --output sbom.cdx.json app:latest\n\n# Generate SBOM in SPDX format\ntrivy image --format spdx-json --output sbom.spdx.json app:latest\n\n# Scan SBOM for vulnerabilities (decouple generation from scanning)\ntrivy sbom sbom.cdx.json --severity CRITICAL,HIGH\n\n# Scan with license detection\ntrivy image --scanners vuln,license --severity HIGH,CRITICAL app:latest\n```\n\n## Key Concepts\n\n| Term | Definition |\n|------|------------|\n| CVE | Common Vulnerabilities and Exposures — standardized identifiers for publicly known security vulnerabilities |\n| Vulnerability DB | Trivy's regularly updated database aggregating CVE data from NVD, vendor advisories, and language-specific sources |\n| Misconfiguration | Security-relevant configuration issue in Dockerfiles, Kubernetes manifests, or IaC templates |\n| SBOM | Software Bill of Materials — complete inventory of all components and dependencies in a container image |\n| Ignore Unfixed | Flag to skip CVEs without available patches, reducing noise from vulnerabilities with no actionable fix |\n| VEX | Vulnerability Exploitability eXchange — machine-readable statements about whether a vulnerability is exploitable in context |\n| Exit Code | Non-zero return code from Trivy when findings exceed the severity threshold, used to fail CI\u002FCD pipelines |\n\n## Tools & Systems\n\n- **Trivy**: Open-source vulnerability scanner by Aqua Security supporting images, filesystems, repos, and IaC\n- **trivy-action**: Official GitHub Action for running Trivy scans in GitHub Actions workflows\n- **Trivy Operator**: Kubernetes operator that continuously scans cluster workloads with Trivy\n- **Grype**: Alternative image scanner by Anchore for comparison and validation of scan results\n- **Harbor**: Container registry with built-in Trivy integration for automatic image scanning on push\n\n## Common Scenarios\n\n### Scenario: Multi-Stage Build with Separate Scan and Push\n\n**Context**: A team builds multi-stage Docker images and needs to scan the final production image before pushing to ECR, while also scanning the build stage for supply chain risks.\n\n**Approach**:\n1. Build the Docker image with `--target production` for the final stage\n2. Run Trivy with `--severity CRITICAL,HIGH --exit-code 1 --ignore-unfixed` to block on exploitable issues\n3. Generate an SBOM in CycloneDX format and store as a build artifact\n4. Upload SARIF results to GitHub Security tab for visibility\n5. Only push to ECR if the Trivy scan exits with code 0\n6. Tag the pushed image with the scan timestamp and Trivy DB version for audit traceability\n\n**Pitfalls**: Scanning only the final stage misses vulnerable packages that were present in build stages and may have influenced the build. Run `trivy fs` on the build context separately. Caching the Trivy DB too aggressively (weekly) means newly published CVEs take days to appear in scans.\n\n## Output Format\n\n```\nTrivy Container Scan Report\n=============================\nImage: app:a1b2c3d4\nBase Image: python:3.12-slim-bookworm\nScan Date: 2026-02-23\nDB Version: 2026-02-23T00:15:00Z\n\nVULNERABILITY SUMMARY:\n  Total: 47\n  Critical: 2\n  High: 5\n  Medium: 18\n  Low: 22\n  Unfixed: 8 (excluded from gate)\n\nCRITICAL FINDINGS:\n  CVE-2025-12345  libssl3    3.0.11-1  3.0.13-1  OpenSSL buffer overflow\n  CVE-2025-67890  curl       7.88.1-10 7.88.1-12 curl HSTS bypass\n\nHIGH FINDINGS:\n  CVE-2025-11111  zlib1g     1.2.13    1.2.13.1  zlib heap buffer overflow\n  CVE-2025-22222  python3.12 3.12.1    3.12.3    CPython path traversal\n  CVE-2025-33333  requests   2.31.0    2.32.0    requests SSRF in redirects\n\nMISCONFIGURATION:\n  DS002  [HIGH]   Dockerfile: USER instruction not set (running as root)\n  DS026  [MEDIUM] Dockerfile: No HEALTHCHECK defined\n\nQUALITY GATE: FAILED (2 Critical, 5 High findings)\n```\n",{"name":5,"tags":25,"author":32,"domain":33,"license":15,"version":34,"nist_csf":35,"subdomain":26,"description":40,"mitre_attack":41},[26,27,28,29,30,31],"devsecops","cicd","trivy","container-security","vulnerability-scanning","secure-sdlc","mahipal","cybersecurity","1.0.0",[36,37,38,39],"PR.PS-01","GV.SC-07","ID.IM-04","PR.PS-04","Integrates Aqua Security's Trivy scanner into CI\u002FCD pipelines to detect OS package and application dependency CVEs, Dockerfile misconfigurations, and issues in filesystems or git repositories, and to enforce severity-based quality gates that block vulnerable images from being deployed. Use when building Docker images in CI\u002FCD and needing automated vulnerability scanning and pass\u002Ffail gates before registry push or production deployment.\n",[42,43,44,45,46],"T1195","T1554","T1059.004","T1610","T1611","main","7540bbccf0c1ded6156a467b02c95b61ad62413f",".agents\u002Fskills\u002Fscanning-containers-with-trivy-in-cicd","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena","Currently exploring the intersection of tech","2026-09-11 03:02:31",{"source":8,"skillName":5,"commands":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add NeelakshSaxena\u002FVayu --skill scanning-containers-with-trivy-in-cicd",{"tool":60,"command":61},"bunx","bunx skills add NeelakshSaxena\u002FVayu --skill scanning-containers-with-trivy-in-cicd",{"tool":63,"command":64},"pnpm","pnpm dlx skills add NeelakshSaxena\u002FVayu --skill scanning-containers-with-trivy-in-cicd","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fscanning-containers-with-trivy-in-cicd\u002FSKILL.md",true,[68,74,78,84,88,92,98],{"path":69,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},"assets\u002Ftemplate.md","ASSET","资产文件",4949,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fscanning-containers-with-trivy-in-cicd\u002Fassets\u002Ftemplate.md",{"path":75,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":77,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":79,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Fapi-reference.md","REFERENCE","参考文档",1951,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fscanning-containers-with-trivy-in-cicd\u002Freferences\u002Fapi-reference.md",{"path":85,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":86,"sourceHtmlUrl":87},"references\u002Fstandards.md",2729,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fscanning-containers-with-trivy-in-cicd\u002Freferences\u002Fstandards.md",{"path":89,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":90,"sourceHtmlUrl":91},"references\u002Fworkflows.md",4264,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fscanning-containers-with-trivy-in-cicd\u002Freferences\u002Fworkflows.md",{"path":93,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":96,"sourceHtmlUrl":97},"scripts\u002Fagent.py","SCRIPT","脚本",6226,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fscanning-containers-with-trivy-in-cicd\u002Fscripts\u002Fagent.py",{"path":99,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":100,"sourceHtmlUrl":101},"scripts\u002Fprocess.py",12006,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fscanning-containers-with-trivy-in-cicd\u002Fscripts\u002Fprocess.py",[103,110,117,124,131,138],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":20},"01M7ACCCVNCFKMA9X6D15X6G98","runpodctl","Runpod CLI for managing GPU\u002FCPU workloads from the terminal — pods, serverless endpoints, templates, network volumes, Hub deploys, models, SSH, and file transfer (send\u002Freceive). Use for terminal\u002FCI\u002Fscripting, Hub browse\u002Fdeploy, SSH setup, `doctor`, or when the Runpod MCP tools are not connected. For structured tool calls in an MCP-enabled session, prefer runpod-mcp.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpodctl\u002FSKILL.md",[],[],{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":20},"01M7ACC63SRHEA5KMCHSMZK2TC","runpod","Start here for any Runpod task — running GPU\u002FCPU pods, deploying serverless endpoints, templates, network volumes, building images, or understanding how Runpod works. Routes to the right skill (runpod-mcp, runpodctl, flash, companion-clis, runpod-usage, runpod-templates, runpod-migrate) and indexes two dozen live-verified end-to-end examples (golden paths) — use it when the lane is unclear, and for any multi-step or provisioning task even when it is not.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod\u002FSKILL.md",[],[],{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":20},"01M7ACC0Q1C89N9BZBV91CTQTF","runpod-usage","How Runpod works and how to work it — pods vs serverless, GPU\u002FVRAM selection, storage, building a container, networking, plus the agentic pod development loop (provision → ssh-exec → set up → poll readiness) and on-pod install hygiene (uv\u002Fapt). Use to answer \"how does X work\", \"which GPU\", \"how do I build a container\", or \"how do I stand up a workload on a pod\". Guidance, not a tool — execute with runpodctl, runpod-mcp, or flash.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-usage\u002FSKILL.md",[],[],{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":130,"publishedAt":20},"01M7ACBRPE345GF5GM5B8P8RRC","runpod-templates","Runpod's official prebuilt pod templates (ComfyUI, PyTorch, and others): what each image ships, which ports and paths it uses, how to pick one, how to pin a version, and what is missing on first boot. Use when a task says \"run \u003CX> on a pod\" and an official template already covers it, instead of building an image — and when a user needs help with or wants to fix something about a Runpod template they are already running (won't boot, can't reach the UI, missing models, wrong CUDA line, broken ComfyUI workflow metadata on imported workflows): start here and route onward. Deploy with runpodctl or runpod-mcp; end-to-end walkthroughs live in the runpod router's golden paths.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-templates\u002FSKILL.md",[],[],{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":137,"publishedAt":20},"01M7ACBJATHKVX1TWES2F44GY8","runpod-migrate","Migrate a codebase from the Runpod GraphQL API or REST v1 to REST v2 — inventory which parts use which API version, rewrite the call sites, flag breaking changes, and verify. Use when someone asks to move to v2, asks what v2 would change, or asks which Runpod API their code is on. For managing infrastructure rather than migrating code, use runpod-mcp or runpodctl.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-migrate\u002FSKILL.md",[],[],{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":144,"publishedAt":20},"01M7ACBC7GHVH6T9YEAPCG2AP8","runpod-mcp","Manage Runpod infrastructure — pods, serverless endpoints, jobs, templates, network volumes, container-registry auth, GPU\u002FCPU catalog, and billing — via the Runpod MCP server's structured tool calls. Use when the Runpod MCP tools (create-pod, list-endpoints, …) are connected in this session, or to connect them (hosted OAuth or local npx). Prefer this over runpodctl for plain infra CRUD when MCP is available; use runpodctl for the terminal, file transfer, or SSH setup.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-mcp\u002FSKILL.md",[],[]]