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

deps/vulnerability-scan

Dependencies are scanned for known vulnerabilities

Severitywarning
Tiers1, 2
Stacksany
Scoperoot
Kindoutcome
Sourcelibrary v0.0.0-20261011205826-ecb4e9b3ffd4
Selected byfleetlint-recommended@0.1.0

Requirement

The task runner (any kind) or a CI workflow runs a dependency vulnerability scanner: govulncheck, pip-audit, cargo deny or cargo audit, npm/pnpm/yarn audit, osv-scanner, trivy, grype, OWASP dependency-check, Snyk, or GitHub dependency review. 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.

See: https://fleetlint.org/baseline/#dependencies


Generated by fleetlint docs from catalog v0.0.0-20261011205826-ecb4e9b3ffd4.