Getting Started
11 items tagged with "getting-started"
Tutorials9
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.
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.
Initialize Vibgrate Config with vg init
Use vg init to create the .vibgrate directory and config file so your scans are repeatable and shareable across the team.
Keep the Vibgrate CLI Current with vg update
Check for and install Vibgrate CLI updates with vg update so your scans use the latest detectors and output improvements.
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.
FAQs2
What is Vibgrate?
Vibgrate is a command-line tool (CLI) that scans your codebase for upgrade drift — the gap between the dependency versions you run and the versions yo...
How do I run my first scan?
Run vg scan in your project directory. The scan recursively discovers projects (package.json, .csproj, pom.xml, requirements.txt), detects runtime ver...