This article explains how to scan a single package or service so you get a DriftScore scoped to exactly the code one team owns. It is for developers working in multi-package repositories or running per-service pipelines.
Overview
When you want drift results for one package rather than a whole repository, you scan that package's directory. You can either change into the directory and run the bare binary, or stay where you are and point the scan with --cwd.
Step-by-step
If you are already inside the package directory, just run:
vg
From anywhere else, target the package with --cwd:
vg scan --cwd packages/checkout
The scan resolves that package's own manifests and lockfile and reports a DriftScore for it alone.
When to scan a single package
- A service has its own deployment cadence and its own pipeline.
- A team wants a gate (for example
--fail-onor--drift-budget) tuned to their package. - You want to compare drift between packages to decide where to invest upgrade effort.
Notes
Remember not to append a trailing path argument to scan. To target a directory, use --cwd; to scan where you are, use bare vg.
Related
See the scanning a monorepo guide, the scanning a subdirectory guide, the setting a drift budget guide, and the scan command reference.