Skill

performing-container-security-scanning-with-trivy

skill:mukul975/anthropic-cybersecurity-skills#performing-container-security-scanning-with-trivy

Runs Trivy across every target type it supports - container images, filesystems, Git repositories, and Kubernetes clusters - for OS and dependency vulnerabilities, IaC misconfiguration, exposed secrets, and licences, generating CycloneDX or SPDX SBOMs. Use when integrating Trivy into CI/CD, deploying the Trivy Kubernetes operator, scanning non-image targets, or triaging results at scale. Keywords: Trivy, trivy k8s, operator, SBOM, CycloneDX, SPDX, misconfig, secret scanning. Do not use for a single Docker image scan - use scanning-docker-images-with-trivy.

SkillsMP

Verdict

Suspicious

Risky behavior the analysis could not rule out.

Analyzed Oct 27, 2026, 22:36 UTC at 54a7988

findings

medium

highest severity

threat classes

4,532

files scanned

67/67

checks satisfied

package advisories

Why this verdict

suspicious: finding skill:skills/performing-container-security-scanning-with-trivy:skills/performing-container-security-scanning-with-trivy/references/api-reference.md:59:SUPPLY

Security findings 1

Supply chain

mediumContextual risklow confidence

The CI/CD integration documentation directs the agent to wire the remote GitHub Action aquasecurity/trivy-action at the mutable @master ref into the user's workflow, so unpinned third-party code executes in the pipeline and can change without review.

skills/performing-container-security-scanning-with-trivy/references/api-reference.md:59

uses: aquasecurity/trivy-action@master

vector:instruction

Counter-argument considered

I could not kill this finding: the reference file, reachable via the declared 'integrating Trivy into CI/CD' use case, gives a copy-paste workflow step that pulls the third-party action at the mutable @master ref, which is not a pinned-install carve-out, is covered by no declared claim (D4 concerns only scanner flags), and forms a concrete source-to-sink chain into the user's pipeline.

Open questions 1

What the analysis could not settle from the code alone.

[file request skills/performing-container-security-scanning-with-trivy/scripts/agent.py] What does the entry point or caller section do - which values feed the image, target_path, scanners, severity, and sbom_format parameters of the trivy commands, and are there any network, credential, or persistence operations in the unshown lines?

Code execution