Getting Started articles for the Vibgrate CLI.
Configure your organization, register a product with digital elements, freeze a shipped release, and run your first exposure check from the Evidence panel — no prior regulatory tooling required.
Step-by-step instructions for installing the Vibgrate CLI on macOS and Linux, including Node-based and curl installer options, plus how to confirm the install works.
How to install the Vibgrate CLI on Windows using npm or the PowerShell installer, then verify that the vg command works in PowerShell and Windows Terminal.
Install the Vibgrate CLI globally or per-project with npm, understand the difference, and confirm the vg command runs your first scan.
Install the Vibgrate CLI using pnpm, yarn, or bun, both globally and as a project dev dependency, then run your first drift scan.
Try the Vibgrate CLI without installing anything by running it through npx. Learn the exact command, when to use it, and its tradeoffs versus a global install.
Install the Vibgrate CLI without a Node package manager using the curl shell installer, then verify the vg command and run your first scan.
Scan a Go module for upgrade drift with the Vibgrate CLI, understand the DriftScore it reports, and set up a baseline so you can track drift over time.
Scan a Rust crate or workspace for upgrade drift with the Vibgrate CLI, read the DriftScore, and capture a baseline for tracking drift over time.
Scan a Composer-based PHP project for upgrade drift with the Vibgrate CLI, understand the DriftScore, and create a baseline to track drift over time.
Scan a Bundler-based Ruby project for upgrade drift with the Vibgrate CLI, read the DriftScore, and capture a baseline to track drift over time.
A guided first scan with the Vibgrate CLI: run the bare command, read the findings and DriftScore, then try structured output and a quality gate.
After your first scan, learn what the DriftScore means, how to read its 0-100 range, and what actions to take based on the result.
Sign the Vibgrate CLI into your workspace from the browser with vg login, confirm you are authenticated, and sign out with vg logout when needed.
Keep the Vibgrate CLI current using the built-in updater or your package manager, then confirm the new version is active.
Cleanly remove the Vibgrate CLI: sign out, uninstall the binary with your package manager, and remove project artifacts you no longer need.
Confirm the Vibgrate CLI is correctly installed: check the version, run a quick scan, and resolve common command-not-found issues.
Set up continuous drift detection in under 10 minutes. Quick-start templates for GitHub Actions, Azure DevOps, GitLab CI, and generic pipelines.
Install the Vibgrate CLI, run your first scan, and understand your DriftScore in under five minutes. This guide covers installation on every major platform and walks through the essential first-scan workflow.
A step-by-step guide to scanning Node.js and TypeScript projects with the Vibgrate CLI — from a single package.json to complex monorepos with multiple workspaces.
Scan .NET solutions and projects for upgrade drift — runtime version lag, NuGet package drift, target framework analysis, and more.
Scan Python projects for dependency drift using requirements.txt, pyproject.toml, and other Python manifests with the Vibgrate CLI.
Scan Java and JVM projects for dependency drift — Maven, Gradle, and Spring Boot projects are all supported by the Vibgrate CLI.