Blog posts from December 2025.
Vibgrate works out of the box with sensible defaults, but every team has different risk tolerances. Learn how to customise thresholds, enable or disable extended scanners, and tailor the configuration to match your organization's upgrade policies.
Peter ChapmanDifferent consumers need different formats. Developers want terminal output. CI systems want SARIF. Managers want Markdown. Automation pipelines want JSON. Vibgrate supports all four — here's when to use each and how to generate them.
Luke GeavesA single scan tells you where you are. A baseline tells you where you started — and whether you are getting better or worse. Learn how to use vibgrate baseline to establish your starting point and track drift trends over weeks and months.
Peter ChapmanMost real-world codebases are not single-language. A typical organization has Node frontends, .NET or Java backends, Python data pipelines, and shared infrastructure. Vibgrate scans all of them in a single pass — here is how it works and what it detects.
Luke GeavesAI coding assistants have evolved from autocomplete tools into autonomous agents capable of multi-file refactoring and cross-language migration. We examine the state of agent-driven code migration in late 2025 and what it means for teams managing large legacy codebases.
Luke GeavesYou ran your first scan — now what? This guide walks through every section of the Vibgrate report output, explains what each finding means, and shows how to turn the Priority Actions list into concrete backlog items.
Peter Chapman