Back to catalog
Static reviewDevelopment

Skill dossier

scanning-containers-with-trivy-in-cicd

Source declaration

Integrates Aqua Security's Trivy scanner into CI/CD 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/CD and needing automated vulnerability scanning and pass/fail gates before registry push or production deployment.

The author's original description, preserved in English. It describes intent, not verified performance.

Integrates Aqua Security's Trivy scanner into CI/CD 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/CD and needing automated vulnerability scanning and pass/fail gates before registry push or production deployment.

developmentreferencesscripts

Research summary

Machine-generated analysis; pending human review

These observations come from deterministic source parsing, not a human security review or controlled task evaluation.

Integrates Aqua Security's Trivy scanner into CI/CD 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/CD and needing automated vulnerability scanning and pass/fail gates before registry push or production deployment. This bilingual summary is generated deterministically from collected source text and file structure; it is pending human editorial review.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Workflow [Source statement; provisional, not tested. Evidence: skills/scanning-containers-with-trivy-in-cicd/SKILL.md:L55]
  • Step 1: Configure Trivy Scanning in GitHub Actions [Source statement; provisional, not tested. Evidence: skills/scanning-containers-with-trivy-in-cicd/SKILL.md:L57]
  • Step 2: Scan Dockerfiles for Misconfigurations [Source statement; provisional, not tested. Evidence: skills/scanning-containers-with-trivy-in-cicd/SKILL.md:L117]
  • Step 3: Integrate with GitLab CI/CD [Source statement; provisional, not tested. Evidence: skills/scanning-containers-with-trivy-in-cicd/SKILL.md:L136]
  • Step 4: Configure Trivy Ignore and Exception Handling [Source statement; provisional, not tested. Evidence: skills/scanning-containers-with-trivy-in-cicd/SKILL.md:L192]
  • Step 5: Implement Database Caching and Offline Scanning [Source statement; provisional, not tested. Evidence: skills/scanning-containers-with-trivy-in-cicd/SKILL.md:L214]
  • Step 6: Generate SBOM and Scan for License Compliance [Source statement; provisional, not tested. Evidence: skills/scanning-containers-with-trivy-in-cicd/SKILL.md:L245]

Limitations & scope

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Relevant for

  • Practitioners evaluating whether to inspect and install the source skill; this audience is inferred from the product context, not measured usage. [Evidence: skills/scanning-containers-with-trivy-in-cicd/SKILL.md:L1-L34]

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
8
Markdown files
5
scripts
2
references
4
Size
52.9 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/scanning-containers-with-trivy-in-cicd/assets/template.mdReference4.8 KB
skills/scanning-containers-with-trivy-in-cicd/LICENSEOther11 KB
skills/scanning-containers-with-trivy-in-cicd/references/api-reference.mdReference1.9 KB
skills/scanning-containers-with-trivy-in-cicd/references/standards.mdReference2.7 KB
skills/scanning-containers-with-trivy-in-cicd/references/workflows.mdReference4.2 KB
skills/scanning-containers-with-trivy-in-cicd/scripts/agent.pyScript6.1 KB
skills/scanning-containers-with-trivy-in-cicd/scripts/process.pyScript11.7 KB
skills/scanning-containers-with-trivy-in-cicd/SKILL.mdInstruction10.5 KB

SKILL.md frontmatter

{
  "name": "scanning-containers-with-trivy-in-cicd",
  "description": "Integrates Aqua Security's Trivy scanner into CI/CD 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/CD and needing automated vulnerability scanning and pass/fail gates before registry push or production deployment.\n",
  "domain": "cybersecurity",
  "subdomain": "devsecops",
  "tags": [
    "devsecops",
    "cicd",
    "trivy",
    "container-security",
    "vulnerability-scanning",
    "secure-sdlc"
  ],
  "version": "1.0.0",
  "author": "mahipal",
  "license": "Apache-2.0",
  "nist_csf": [
    "PR.PS-01",
    "GV.SC-07",
    "ID.IM-04",
    "PR.PS-04"
  ],
  "mitre_attack": [
    "T1195",
    "T1554",
    "T1059.004",
    "T1610",
    "T1611"
  ]
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Decision

    When to Use

    Source-described decision candidate under “When to Use”; not verified execution.

  2. 02
    Action

    Workflow

    Source-described action candidate under “Workflow”; not verified execution.

  3. 03
    Action

    Step 1: Configure Trivy Scanning in GitHub Actions

    Source-described action candidate under “Step 1: Configure Trivy Scanning in GitHub Actions”; not verified execution.

  4. 04
    Action

    Step 2: Scan Dockerfiles for Misconfigurations

    Source-described action candidate under “Step 2: Scan Dockerfiles for Misconfigurations”; not verified execution.

  5. 05
    Action

    Step 3: Integrate with GitLab CI/CD

    Source-described action candidate under “Step 3: Integrate with GitLab CI/CD”; not verified execution.

  6. 06
    Action

    Step 4: Configure Trivy Ignore and Exception Handling

    Source-described action candidate under “Step 4: Configure Trivy Ignore and Exception Handling”; not verified execution.

Inspect all extracted workflow candidates (19 candidate steps)
  1. 07
    Action

    Step 5: Implement Database Caching and Offline Scanning

    Source-described action candidate under “Step 5: Implement Database Caching and Offline Scanning”; not verified execution.

  2. 08
    Action

    Step 6: Generate SBOM and Scan for License Compliance

    Source-described action candidate under “Step 6: Generate SBOM and Scan for License Compliance”; not verified execution.

  3. 09
    Action

    Use Trivy to generate Software Bill of Materials alongside vulnerability scanning.

    Source-described action candidate under “Step 6: Generate SBOM and Scan for License Compliance”; not verified execution.

  4. 10
    Action

    Key Concepts

    Source-described action candidate under “Key Concepts”; not verified execution.

  5. 11
    Action

    Tools & Systems

    Source-described action candidate under “Tools & Systems”; not verified execution.

  6. 12
    Action

    Common Scenarios

    Source-described action candidate under “Common Scenarios”; not verified execution.

  7. 13
    Output

    Build the Docker image with `--target production` for the final stage

    Source-described output candidate under “Scenario: Multi-Stage Build with Separate Scan and Push”; not verified execution.

  8. 14
    Action

    Run Trivy with `--severity CRITICAL,HIGH --exit-code 1 --ignore-unfixed` to block on exploitable issues

    Source-described action candidate under “Scenario: Multi-Stage Build with Separate Scan and Push”; not verified execution.

  9. 15
    Action

    Generate an SBOM in CycloneDX format and store as a build artifact

    Source-described action candidate under “Scenario: Multi-Stage Build with Separate Scan and Push”; not verified execution.

  10. 16
    Input

    Upload SARIF results to GitHub Security tab for visibility

    Source-described input candidate under “Scenario: Multi-Stage Build with Separate Scan and Push”; not verified execution.

  11. 17
    Decision

    Only push to ECR if the Trivy scan exits with code 0

    Source-described decision candidate under “Scenario: Multi-Stage Build with Separate Scan and Push”; not verified execution.

  12. 18
    Action

    Tag the pushed image with the scan timestamp and Trivy DB version for audit traceability

    Source-described action candidate under “Scenario: Multi-Stage Build with Separate Scan and Push”; not verified execution.

  13. 19
    Output

    Output Format

    Source-described output candidate under “Output Format”; not verified execution.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Attention recommended

35 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useNot observed
High

File deletion is described or implemented

Deletion syntax occurs in this line, including possible documentation. Review its exact target, recursive scope, and safeguards. The analyzer did not execute it. This rule matched 1 location(s) in the collected text; 1 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Medium

Network access is mentioned

14 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 14 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Note

File modification is described or implemented

20 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 20 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
Inspect the pinned source at https://github.com/mukul975/Anthropic-Cybersecurity-Skills/blob/54a798831d2266a3ca61ce68a7acb80b81160d57/skills/scanning-containers-with-trivy-in-cicd/SKILL.md and follow the source repository's installation instructions. No installation was performed or verified by this static analyzer. Source license: Apache-2.0.

Prerequisites

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Example prompts

Not provided

A decision, with its limits attached

Strengths

  • The snapshot contains 8 collected file(s), 5 Markdown file(s), and 2 script file(s), enabling source-level inspection. [Evidence: skills/scanning-containers-with-trivy-in-cicd/SKILL.md:L1]

Considerations

  • No functional, security, or model-quality result has been established. Human review must inspect source context and all cited findings before installation or publication.
Research conclusion

Provisional deterministic static inventory only; pending human editorial review and, separately, controlled evaluation. No install recommendation, security assurance, or effectiveness claim is made.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

mukul975Anthropic-Cybersecurity-Skillsskills/scanning-containers-with-trivy-in-cicd
Source type
Community
Commit
54a798831d2266a3ca61ce68a7acb80b81160d57
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
Apache-2.0
Repository stars
36,446
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.