fleetlint Policy for a fleet of repositories
v0.11 (latest)
Getting started

deps/unused-check

Unused dependencies are detected

A capability: each stack checks it with its own tools, and every implementation that runs must pass. Implemented for flutter, go, hugo, java, kotlin, node, php, python, rust.

Severityinfo
Tiers1
Stacksany
Scopeeach
Kindcapability
Sourcelibrary v0.8.0
Selected byfleetlint-recommended@v0.8.0

Requirement

A task-runner recipe or a CI step runs the stack’s unused-dependency check, so a dependency nothing imports is removed instead of carried (and audited, and updated) forever. 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.

Why

Every declared dependency is attack surface and update churn; one nothing uses is pure cost.

Fix

Add the stack’s unused-dependency check to the audit target (see https://fleetlint.org/stacks/).

Agent instruction: Add the stack’s unused-dependency checker to the audit target; remove the dependencies it reports in a separate change after confirming nothing loads them dynamically.

Sources


Generated by fleetlint docs from catalog v0.8.0.