This glossary defines the terms you will encounter across Vibgrate documentation and command output. It is for anyone new to the CLI, and a handy refresher for returning users.
Core terms
- Vibgrate CLI — The command-line scanner, installed as the
vgbinary (package@vibgrate/cli). A barevgscans the current directory. - DriftScore — The 0-100 metric summarizing how far your dependencies and platform have drifted from current, well-supported versions. Higher means more drift.
- Upgrade drift — The gap between what your project uses today and the maintained, current state of its dependencies and platform.
- Baseline — A saved snapshot of scan state used for delta comparison and drift gates. Created with
vg baseline. - Drift budget — A threshold that, when exceeded, can fail a build, set with
vg scan --drift-budget 60.
Platform and uploads
- Vibgrate Cloud — The hosted dashboard at dash.vibgrate.com for team visibility and trends. Results reach it via
vg push. - DSN token — An HMAC-signed token for authenticating dashboard uploads, created with
vg dsn create.
Code map and AI context
- Code map — The graph artifact built from your source that powers queries like
vg show,vg ask, andvg impact. Built withvg build. - Vibgrate Graph — The dependency and architecture graph capability behind those queries.
- Vibgrate AI Context — The local, offline MCP server started with
vg serve, serving your code map, drift, and version-correct library docs to any AI assistant. - Free Dev Docs Library — Version-correct library docs pinned to your lockfile, accessed with
vg lib.
Outputs
- SBOM — A Software Bill of Materials (CycloneDX or SPDX) exported with
vg sbom export. - SARIF — A standard format for code-scanning surfaces, produced with
vg scan --format sarif.
Related
- Getting Started
- DriftScore explained
- Command cheat-sheet