trivy
$ brew install trivyImage scanning, vulns, and iac checks from the terminal.
- trivy fits infra well, especially for image scanning, vulns, and iac checks from the terminal.
- It is the official CLI from Aqua Security.
- Good for scripts and agents.
- Good fit for coding-agent workflows and repeatable scripts.
- Structured output is available for automation and parsing.
Trivy guide
The official CLI from Aqua Security. Image scanning, vulns, and iac checks from the terminal. Supports structured output — good for scripts and agents.
Open CLI packages the install path, verify step, and safe-start workflow so this tool can move from “interesting CLI” to something you can actually use. It also integrates with skills.sh so each CLI comes with the right companion skills, not just a binary and a docs link.
When to apply
- image scanning, vulns, and iac checks from the terminal.
- You want security scanning you can script with structured output.
- You need image scanning.
- You need vulns.
- You need iac checks.
Quick reference
brew install trivytrivy --versiontrivy image node:20Open CLI × skills.sh
Open CLI integrates trivy with the right skills.sh companions so you get the tool and the workflow together.
Security Best Practices
Recommended pairingOpen CLI recommends this skills.sh skill because it fits security workflows. Add safer defaults when a CLI touches secrets, auth, or sensitive systems.
$ npx skills add https://github.com/supercent-io/skills-template --skill security-best-practicesUse trivy together with the Security Best Practices skills.sh skill. Start with inspection or dry-run commands, summarize any risk, and ask before actions with side effects.
Why this tool
- trivy fits infra well, especially for image scanning, vulns, and iac checks from the terminal.
- It is the official CLI from Aqua Security.
- Good for scripts and agents.
Watch-outs
- Run the verify command first.
Example workflow
1. trivy image node:20Safe start
Install trivy.
Run `trivy --version` first.
Start with `trivy image node:20`.
Install the infra CLI and verify kubeconfig, Docker context, or cloud credentials.