fleetlint Policy for a fleet of repositories
v0.8
Getting started

deps/vulnerability-scan

Dependencies are scanned for known vulnerabilities

A capability: each stack checks it with its own tools. Implemented for any, cpp, dotnet, go, hugo, java, kotlin, node, php, python, ruby, rust.

Combine: all. Every implementation that runs must pass: each stack in the repository meets the requirement with its own tools.

Severitywarning
Tiers1, 2
Stacksany
Scopeeach
Kindcapability
Sourcelibrary v0.5.0
Selected byfleetlint-recommended@v0.5.0

Requirement

A task-runner recipe or a CI step runs a dependency vulnerability scanner: the stack’s native tool or a stack-neutral one (osv-scanner, trivy, grype, Snyk, GitHub dependency review, GitLab dependency scanning). Comments, echo lines and lines that only install the tool do not count. For a workspace member the repository’s CI and the Makefile, justfile or Taskfile of a parent directory count as well. Another scanner is added with accept:.

Why

A lockfile pins yesterday’s versions; only a scan says which of them are known to be exploitable today.

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.

Sources


Generated by fleetlint docs from catalog v0.5.0.