Drift
58 items tagged with "drift"
Tutorials51
Install the Vibgrate CLI Globally with npm
Install @vibgrate/cli globally with npm so the vg command is available everywhere, then confirm the install with a quick scan.
Try the Vibgrate CLI with npx (No Install)
Run a one-off Vibgrate drift scan using npx without installing anything, ideal for trying the CLI or running it in disposable environments.
Install the Vibgrate CLI with pnpm, yarn, or bun
Install @vibgrate/cli globally using pnpm, yarn, or bun and verify the vg command works regardless of which package manager you prefer.
Run the Vibgrate CLI with Docker
Run a Vibgrate drift scan inside Docker by mounting your project, keeping the scan isolated from your host toolchain and reproducible in CI.
Run Your First Vibgrate Scan on the Current Directory
Run your very first Vibgrate drift scan with a bare vg command and learn what the scan looks at and what it produces.
Understand Your DriftScore
Learn what the DriftScore measures, how to read its risk levels, and how to use it as the headline metric for upgrade health.
Read and Interpret Vibgrate Scan Output
Make sense of the default Vibgrate scan output: the results table, the findings it lists, and the DriftScore that summarizes them.
Add Vibgrate to a GitHub Actions Workflow
Run the Vibgrate CLI on every push and pull request with GitHub Actions so upgrade drift is scanned automatically in CI.
Gate Pull Requests on a Drift Budget
Use vg scan --drift-budget in CI to fail pull requests that exceed a DriftScore threshold, keeping upgrade drift inside an agreed limit.
Upload Vibgrate SARIF to GitHub Code Scanning
Produce SARIF output with vg scan --format sarif and upload it to GitHub code scanning so drift findings appear in the Security tab and on PRs.
Run Vibgrate in a GitLab CI Pipeline
Add a drift-scanning job to .gitlab-ci.yml using the Vibgrate CLI, with artifacts and a SARIF report for merge requests.
Run Vibgrate in an Azure DevOps Pipeline
Add a Vibgrate drift scan to an Azure Pipelines YAML pipeline for .NET and Node.js projects, with a drift budget gate.
Run Vibgrate in a Jenkins Pipeline
Add a drift-scanning stage to a Jenkins declarative pipeline with the Vibgrate CLI and fail the build on a drift budget.
Run Vibgrate on CircleCI
Add a Vibgrate drift-scanning job to a CircleCI config using a Node executor, store the SARIF report, and gate on a drift budget.
Run Vibgrate in Bitbucket Pipelines
Add a drift-scanning step to bitbucket-pipelines.yml with the Vibgrate CLI, keep the SARIF report as an artifact, and gate on a drift budget.
Fail CI Builds with vg scan --fail-on
Use the --fail-on flag to make the Vibgrate CLI return a non-zero exit code at a chosen severity so CI builds fail on real problems.
Schedule Nightly Drift Scans in CI
Run a scheduled Vibgrate scan every night with a GitHub Actions cron trigger and push the DriftScore to Vibgrate Cloud for trend tracking.
Comment Drift Results on Pull Requests
Generate a Markdown drift report with the Vibgrate CLI and post it as a pull request comment so reviewers see the DriftScore in context.
Scan Only Changed Files in CI
Use vg scan --changed-only to focus pull request scans on modified files for faster, more relevant drift feedback in CI.
Cache Vibgrate Between CI Runs
Persist the Vibgrate cache directory across CI runs so repeated scans reuse prior work and finish faster.
Matrix Drift Scans Across a Monorepo
Use a CI matrix to run a Vibgrate scan per package in a monorepo, with the --cwd flag targeting each workspace directory.
Push Drift Results to Vibgrate Cloud from CI
Upload Vibgrate CLI scan results to Vibgrate Cloud from your pipeline with vg scan --push, authenticated by a DSN secret, for team-wide trend tracking.
Run vg in a Pre-Commit Hook
Add the Vibgrate CLI to a pre-commit hook so drift is caught locally before a commit ever reaches CI.
Create Your First Drift Baseline with vg baseline
Capture a point-in-time snapshot of your project's upgrade drift so future scans can be compared against a known-good reference.
Scan Against a Drift Baseline for Delta Comparison
Compare a fresh scan against a saved baseline with vg scan --baseline to see exactly how your upgrade drift changed since the snapshot.
Set a Drift Budget to Cap Acceptable Upgrade Drift
Use vg scan --drift-budget to define a maximum acceptable drift level and turn your DriftScore into an enforceable quality gate.
Ratchet Your Drift Budget Down Over Time
Progressively tighten vg scan --drift-budget release after release so your project's upgrade drift only ever moves in one direction: down.
Fail CI When New Drift Appears Against a Baseline
Wire vg scan --baseline into your pipeline so any new upgrade drift introduced by a change fails the build before it merges.
Track Your Drift Trend Across Releases
Baseline each release and compare scans against it to see whether your DriftScore is improving or degrading over the project's lifetime.
Baseline a Monorepo One Package at a Time
Create and scan per-package drift baselines in a monorepo so each workspace owns its own drift ceiling instead of one shared number.
Update and Refresh an Existing Drift Baseline
Re-run vg baseline to refresh your snapshot after intentional, reviewed changes so the baseline reflects the new accepted normal.
Initialize a Project With a Baseline Using vg init --baseline
Bootstrap Vibgrate and create an initial drift baseline in one step with vg init --baseline so new projects start with a reference snapshot.
Compare Two Drift Baselines to Measure Change
Pin a scan to an older baseline file while a newer one exists to measure exactly how much your upgrade drift moved between two points in time.
Enforce Per-Team Drift Budgets
Give each team its own vg scan --drift-budget so ownership and accountability for upgrade drift map cleanly to the people who can fix it.
Prevent Drift Regressions on a Legacy Module
Pin a baseline to a legacy module and gate it so the old code can't get worse, even while you avoid a risky full rewrite.
Interpret Baseline Diff Output
Learn how to read the delta from vg scan --baseline so you can tell new drift apart from carried-over drift and act on the right items.
Commit the Drift Baseline to Your Repository
Check your baseline file into version control so every developer and CI run compares against the same shared drift reference.
Combine a Drift Scan and SBOM Export in One CI Job
Run a single CI job that scans for drift with a failing gate and exports a CycloneDX SBOM, covering quality and inventory together.
Scan a Node.js/TypeScript Project for Upgrade Drift
Run your first Vibgrate CLI scan on a Node.js/TypeScript project to get a DriftScore and a prioritized list of upgrade risks.
Scan a .NET Solution for Upgrade Drift
Point Vibgrate CLI at a .NET solution to measure upgrade drift across projects and produce a SARIF report for Azure DevOps.
Scan a Python Project for Upgrade Drift
Use Vibgrate CLI to scan a Python project for upgrade drift, read the DriftScore, and export JSON for further processing.
Scan a Java/Maven Project for Upgrade Drift
Run Vibgrate CLI against a Java/Maven project to measure upgrade drift and export SARIF and Markdown reports.
Scan a Go Module for Upgrade Drift
Use Vibgrate CLI to scan a Go module for upgrade drift, read the DriftScore, and export results for CI.
Scan a Rust Crate for Upgrade Drift
Run Vibgrate CLI on a Rust crate to measure upgrade drift from Cargo dependencies and export JSON for tooling.
Scan a PHP Project for Upgrade Drift
Use Vibgrate CLI to scan a PHP project for upgrade drift across Composer dependencies and produce a shareable report.
Scan a Ruby Project for Upgrade Drift
Run Vibgrate CLI on a Ruby project to measure upgrade drift across Bundler gems and export results for CI.
Scan a Polyglot Monorepo for Upgrade Drift
Scan a multi-language monorepo with Vibgrate CLI to get one DriftScore across every ecosystem and gate the whole repo in CI.
Generate a Human-Readable Drift Report with vg report
Turn raw scan artifacts into a shareable Markdown, text, or JSON drift report using vg report so stakeholders can read your DriftScore at a glance.
Push Scan Results to Vibgrate Cloud
Upload your local scan results to Vibgrate Cloud with vg push or vg scan --push so the whole team can see drift trends in one dashboard.
View Drift on the Vibgrate Cloud Dashboard
After pushing a scan, learn to read your DriftScore, risk levels, and drift contributors on the Vibgrate Cloud dashboard.
Track Drift Trends Over Time in Vibgrate Cloud
Push scans regularly so Vibgrate Cloud builds a DriftScore trend line, letting you see whether your codebase is drifting toward or away from risk.
Glossaries7
Software Drift
Software drift is the growing gap between the dependencies, runtimes, and frameworks a codebase actually uses and their current, supported versions.
DriftScore
DriftScore is Vibgrate’s 0–100 measure of maintainability drift — how far a stack has moved from current, supported baselines — where 0 is fully current and 100 is maximum drift.
Code Drift
Code drift is how far a codebase — and the AI writing in it — has moved away from current, correct, well-understood truth: current versions, correct APIs, and an accurate picture of the code's own structure.
Dependency Drift
Dependency drift is the growing gap between the dependency versions a project declares and the current, supported releases of those same packages.
AI Context Drift
AI context drift is the gap between the context an AI coding assistant works from — its training data and generic docs — and the exact versions and structure of the codebase it is editing.
Drift Budget
A drift budget is a maximum acceptable DriftScore that a project agrees not to exceed, enforced automatically in CI so drift cannot quietly grow back.
Software Currency
Software currency is how up to date a system's components are relative to their current, supported releases — the positive framing of low drift.