deps/vulnerability-scan/any
Dependencies are scanned for known vulnerabilities
The stack-neutral implementation of deps/vulnerability-scan: it checks stacks without an implementation of their own, and its satisfiers count for every stack.
| Severity | warning |
| Tiers | 1, 2 |
| Stacks | any |
| Scope | each |
| Kind | outcome |
| Source | library v0.1.0 |
| Selected by | fleetlint-recommended@v0.1.0 |
Requirement
A task-runner recipe or a CI step runs a stack-neutral vulnerability scanner over the dependencies: osv-scanner, trivy (fs, repo, rootfs, image or sbom), grype, snyk test, GitHub dependency review or GitLab’s dependency scanning template. Comments, echo lines and lines that only install the tool do not count.
Why
A lockfile pins yesterday’s versions; only a scan says which of them are known to be exploitable today.
Parameters
runners:[../Makefile ../justfile ../Justfile ../Taskfile.yml ../Taskfile.yaml ../../Makefile ../../justfile ../../Justfile ../../Taskfile.yml ../../Taskfile.yaml ../../../Makefile ../../../justfile ../../../Justfile ../../../Taskfile.yml ../../../Taskfile.yaml]skip:^\s*[@+-]*\s*(\{\{[^}]*\}\}\s*|\$[({][A-Za-z_]+[)}]\s*)?(#|//|echo\b|printf\b|(sudo\s+)?(go (install|get)|cargo b?install|pipx? install|pip3 install|python3? -m pip install|uv (tool |pip )?(install|add)|(npm|pnpm|yarn|bun) (i|install|add|global add)|gem install|bundle add|brew install|dotnet tool (install|update)|composer (global )?require|apt(-get)? install|curl|wget)\b[^;&]*$)
Fix
Add the stack’s scanner to the audit target (see https://fleetlint.org/stacks/) so check runs it.
Agent instruction: Add the stack’s vulnerability scanner to the audit target of the task runner; use osv-scanner against the lockfile when the stack has no native tool. Do not fix the findings in the same change; list them.
See: https://fleetlint.org/baseline/#dependencies
Generated by fleetlint docs from catalog v0.1.0.