lazytrivy is a terminal UI wrapper for Trivy that lets you run Trivy scans without remembering all the command arguments. It now uses the latest Trivy binary directly (no Docker image required).
Inspired by Jesse Duffield's superb tools (lazydocker, lazynpm, lazygit).
- Image Scanning
- Scan all images on your system
- Scan a single image
- Scan a remote image
- File System Scanning
- Scan a filesystem for vulnerabilities, misconfigurations, and secrets
- Kubernetes Scanning (Experimental)
- Scan K8s resources for vulnerabilities and misconfigurations (experimental, subject to user feedback)
lazytrivy provides a fast, interactive terminal UI for running Trivy scans. It displays results in a clear, navigable interface and helps you select images, filesystems, or Kubernetes resources to scan. Trivy is run directly (no Docker required), so you always get the latest features and performance.
Trivy will periodically download the latest vulnerability database. lazytrivy maintains a cache, but if you experience a delay, it's likely Trivy is updating its DB.
If you have Go installed:
go install github.com/owenrumney/lazytrivy@latestGet the latest releases from GitHub
Optionally, add a config file at ~/.config/lazytrivy/config.yml:
vulnerability:
ignoreunfixed: false
filesystem:
scansecrets: true
scanmisconfiguration: true
scanvulnerabilities: true
cachedirectory: ~/.cache
debug: true
trace: falseSettings can be adjusted via the UI by pressing the , key at any time.
By setting debug to true, additional logs will be generated in /tmp/lazytrivy.log
lazytrivy is easy to use. Run it with:
lazytrivy --helpAvailable Commands:
imageLaunch lazytrivy in image scanning modefilesystemLaunch lazytrivy in filesystem scanning modek8sLaunch lazytrivy in Kubernetes scanning mode (experimental)helpHelp about any command
Flags:
--debugLaunch with debug logging--traceLaunch with trace logging
Use lazytrivy [command] --help for more information about a command.
Logs are generated in $HOME/.lazytrivy/logs/lazytrivy.log (default level: info). Use the --debug flag for more details, or --trace for verbose output.
You can start lazytrivy in a specific mode using image, filesystem, or k8s:
For example, to scan a specific filesystem folder:
lazytrivy filesystem --path /home/owen/code/github/owenrumney/exampleTo scan Kubernetes resources (experimental):
lazytrivy k8s --context my-kube-context


