Back to Tags

Cli

9 items tagged with "cli"

Filter by type:

FAQs9

FAQ

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...

FAQ

How do I install the Vibgrate CLI?

Install as a dev dependency in your project: npm install -D @vibgrate/cli (or use pnpm, yarn, bun). You can also run without installing using npx: npx...

FAQ

How do I run my first scan?

Run vibgrate scan . in your project directory. The scan recursively discovers projects (package.json, .csproj, pom.xml, requirements.txt), detects run...

FAQ

What does the vibgrate init command do?

The vibgrate init command sets up Vibgrate in your project by creating a .vibgrate/ directory for scan artifacts and baselines, plus a vibgrate.config...

FAQ

What flags does the scan command support?

Key flags: --format (text/json/sarif/md), --out (output file), --fail-on (error/warn - exit code 2 if findings exist), --baseline (compare against bas...

FAQ

How do I upload scan results to the dashboard?

Use vibgrate push after running a scan, or combine them with vibgrate scan . --push. The DSN is read from VIBGRATE_DSN environment variable or pass wi...

FAQ

How do I generate reports from existing scans?

Use vibgrate report to render existing scan artifacts into different formats without re-scanning. By default, it reads .vibgrate/scan_result.json. Use...

FAQ

How do I export SBOMs from Vibgrate scans?

Use vibgrate sbom export to emit CycloneDX or SPDX SBOMs from scan artifacts. Example: vibgrate sbom export --format cyclonedx --out sbom.cdx.json. Us...

FAQ

How do I update the Vibgrate CLI?

Run vibgrate update to check for and install updates. Use --check to see if updates are available without installing. For project installs: npm update...