Driftscore
25 items tagged with "driftscore"
Tutorials23
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.
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.
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.
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.
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.
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.
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 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 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.
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.
Export JSON for Custom Dashboards
Produce machine-readable JSON with vg scan --format json or vg report --format json and feed your DriftScore into custom dashboards and BI tools.
Generate an Executive Drift Summary
Combine vg report with Vibgrate Cloud trends to produce a concise, leadership-ready summary of DriftScore and direction across your repositories.
Glossaries2
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.
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.