Trivy Security Scanner
ReviewAudited by ClawScan on May 1, 2026.
Overview
This is a coherent Trivy scanner skill, but using it may inspect source code, secrets, and Kubernetes cluster state and may require installing Trivy from external package sources.
Before using this skill, verify Trivy installation commands, scan only the images, paths, repositories, or clusters you intend, confirm Kubernetes context and permissions, be cautious with secret-scan results, and remove temporary JSON reports from /tmp after triage.
Findings (4)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
The agent may inspect filesystems, images, IaC, or cluster resources selected for scanning.
The skill directs the agent to run local command-line scans against user-provided targets. This is central to the scanner purpose, but users should confirm the target and command before scanning sensitive environments.
Run the appropriate Trivy scan type with JSON output for structured analysis: ... trivy fs --format json --output /tmp/trivy-fs.json ... /path/to/project
Run scans only on intended targets, review generated commands, and avoid broad filesystem or cluster scans unless that is explicitly desired.
Using this on a cluster may expose workload, image, and misconfiguration details available to the current Kubernetes identity.
A Kubernetes cluster scan can use the user's existing cluster access and may enumerate running workloads across the cluster. This is purpose-aligned, but it is broad account/environment access.
Kubernetes cluster — scan running workloads ... trivy k8s --format json --report all --severity CRITICAL,HIGH cluster
Confirm the active Kubernetes context, namespace, and permissions before running cluster scans; prefer least-privilege read-only access where possible.
A user following the setup changes system package sources and installs software with elevated privileges.
The documented setup installs Trivy from an external repository using privileged package-manager commands. This is expected for Trivy setup, but it is not represented as a formal install spec and is not version-pinned.
wget -qO - https://aquasecurity.github.io/trivy-repo/deb/public.key | gpg --dearmor | sudo tee /usr/share/keyrings/trivy.gpg ... sudo apt-get update && sudo apt-get install trivy
Install Trivy from the official Aqua Security instructions, verify repository keys and URLs, and consider pinning or approving the version before installation.
Scan reports may include sensitive dependency, misconfiguration, path, or secret-finding information that could enter the agent context or remain in temporary files.
The filesystem scan includes secret and misconfiguration scanning and stores structured results locally for later parsing and AI triage. This is aligned with security scanning, but the results can contain sensitive security context.
--scanners vuln,secret,misconfig,license ... --output /tmp/trivy-fs.json
Limit scans to intended project paths, avoid sharing raw secret findings unnecessarily, and delete temporary Trivy JSON reports when they are no longer needed.