Vibgrate Config File: A Deep Reference

This article is a deeper reference for the Vibgrate configuration file. It is for developers who have run vg init and want to understand how the config shapes scans across a team. For a conceptual overview, see the Configuration help page.

Where config lives

Running vg init creates a .vibgrate directory and a configuration file in your project root:

vg init

You can also initialize with a baseline in one step:

vg init --baseline

Committing the config makes scans reproducible for every contributor and in CI.

What the config controls

The configuration file (vibgrate.config.ts) is the place to express project-wide intent, including:

• Thresholds — drift gates and the DriftScore levels that matter for your project.
• Scanner toggles — enable or disable extended scanners such as the platform matrix, dependency graph, and security posture scanners.
• Exclusions — directories and patterns to skip during analysis.

Because config is checked into the repository, everyone scans the same way and CI matches local results.

Config vs. flags

Flags override config for a single run. For example, you can keep a default drift budget in config but tighten it for one pipeline:

vg scan --drift-budget 60

Use config for durable, team-wide defaults and flags for one-off overrides.

Baselines and config

Config works alongside baselines. A baseline snapshot stores scan state for delta comparison; config controls how that scan is produced. Point a scan at a baseline explicitly when needed:

vg scan --baseline .vibgrate/baseline.json

Keeping config healthy

• Review excluded paths periodically so you do not silently hide drift.
• Treat threshold changes like code changes — review them in pull requests.
• Re-run vg init only when starting fresh; editing the existing file is normal day-to-day.

Related

• Configuration help page
• Drift Baselines and Fitness Functions
• The vg init and vg scan command pages