Enabling and Focusing Scanners for a Scan

By default a Vibgrate scan runs the full set of scanners, but you can control which ones run and narrow a scan to the parts of your project you care about. This reference explains the levers available and when to use them. It is for developers tuning local runs and teams standardizing CI behavior.

Default behavior

Run in the project root and Vibgrate scans the current directory with its standard scanner set:

vg

This is the right starting point for most projects. The full set produces a complete DriftScore and the broadest set of findings.

Focusing a scan

When you want a tighter, faster run, narrow the scope:

• Limit the run to recently changed files for fast feedback during development:

vg scan --changed-only

• Exclude paths that should not contribute to the result, such as vendored or generated directories:

vg scan --exclude node_modules

Focusing improves signal by removing noise from code you do not own or maintain, and it speeds up runs in large repositories.

Persisting configuration

For settings you want every run and every teammate to share, use a configuration file rather than remembering flags. Initialize Vibgrate in the project to create the configuration:

vg init

The configuration file is where scanner toggles and exclusions belong so behavior is consistent locally and in CI. See the Configuration reference for the available options. Keeping configuration in the repository means a scan run by a teammate or by your pipeline produces comparable results.

Why focusing matters

A scan that includes generated code, vendored dependencies, or unrelated subprojects dilutes the DriftScore and buries the findings that matter. Excluding those paths sharpens both the score and the action list. Limiting to changed files gives developers fast, relevant feedback without waiting for a full scan, while CI runs the full set for completeness.

Tips

• Use a full scan for CI and the canonical DriftScore; use focused scans for local iteration.
• Put exclusions in configuration, not in ad-hoc flags, so they are shared and reviewable.
• Re-run a full scan before relying on the score for reporting.

Related

See the Configuration reference for scanner toggles and exclusions, the Extended Scanners Overview for what each scanner does, and Output Formats for choosing how results are emitted.