This FAQ answers the questions developers ask most often about the Vibgrate CLI. It is a fast on-ramp; each answer links to a fuller article.
How do I scan my project?
Run the CLI in your project directory. A bare command scans the current directory:
vg
Can I try it without installing?
Yes. Use the no-install form for a one-off run:
npx @vibgrate/cli scan
Do I need an account?
No. Local scans, code-map queries, and the Free Dev Docs Library work without an account and without uploading anything. You only sign in (vg login) when you want to push results to Vibgrate Cloud for team trends.
What is the DriftScore?
The DriftScore is a 0-100 measure of how far your dependencies and platform have drifted from current, well-supported versions. Higher means more drift. See DriftScore explained.
How do I fail a build on too much drift?
Set a gate. Either fail on a severity or set a drift budget:
vg scan --fail-on error
vg scan --drift-budget 60
How do I track change over time instead of absolute state?
Create a baseline and scan against it:
vg baseline
vg scan --baseline .vibgrate/baseline.json
Can it run fully offline?
Yes. Scans run locally, and code-map queries are offline after the first use. Force local-only behavior with:
vg scan --offline
How do I get an SBOM?
Export CycloneDX or SPDX:
vg sbom export --format cyclonedx --out sbom.cdx.json
How do I feed my code to an AI assistant?
Run Vibgrate AI Context, the local offline MCP server, and wire it into your assistant:
vg serve
vg install
Related
- Getting Started and DriftScore explained
- Command cheat-sheet and CLI glossary
- Proxy and offline configuration