How aquasecurity/trivy-action works
Trivy Action adapts a GitHub Actions invocation into a Trivy scan: users select a scan type and target, the action arranges Trivy setup and optional cache handling, and Trivy produces scan output. The README documents image, filesystem, repository, rootfs, IaC, tarball, SBOM, template, and private-registry use cases, plus SARIF for GitHub Code Scanning. Source excerpts were unavailable, so the graph captures documented relationships only; it does not infer how entrypoint.sh implements them.
Main entry points: action.yaml Trivy Action
Components 8
Action orchestration
- Trivy Action
action.yaml - Action entrypoint
entrypoint.sh - Trivy setup
Trivy scanning
- Trivy scanner
- Scan targets
- Scan results
Cache management
- Actions cache
Other components
- Workflow author
Connections 7
- Workflow author → Trivy Action: configures
README.md - Trivy Action → Trivy setup: sets up
README.md - Trivy Action → Actions cache: restores cache
README.md - Trivy Action → Trivy scanner: runs scan
README.md - Trivy scanner → Scan targets: scans
README.md - Trivy scanner → Scan results: produces
README.md - Trivy Action → Actions cache: saves cache
README.md