Third-party package dependencies · Dependency vetting

Remove unused dependencies

When it fails: The project declares dependencies it does not use.

CB-DEP-VET-003lowdraftpartialprofile baseline

Status draft: not part of any release yet, may still change.

Description

Dependencies that are no longer imported or used are removed from manifests and lockfiles. This is checked regularly.

Rationale

Unused dependencies still get installed, still run install scripts, still show up in vulnerability reports, and still can be compromised. Removing them is the cheapest risk reduction.

Impact

None known.

Audit

  1. Run an unused-dependency analysis on each project.
  2. Check findings are handled.

Remediation

  1. Remove unused dependencies and regenerate the lockfile.
  2. Run the analysis periodically or in the pipeline.

References

Mappings

FrameworkIDRelationNote
NIST SP 800-53 Rev. 55.1.1CM-7related

How this control relates to the other framework's: equivalent, stricter, looser, partial or related.

Threats mitigated

People and lifecycle

AuthorsAlice
Introduced inv1.0.0
Created, updated2026-10-16, 2026-10-16