Blog posts from November 2025.
Vibgrate reduces your entire codebase's upgrade health to a single number. But how is that number calculated, what does each component measure, and how should you interpret it? This post breaks down the Upgrade Drift Score in detail.
Peter ChapmanYou do not need to install anything, create an account, or configure a single file. One command gives you a complete picture of your codebase's upgrade health. Here is how to run your first Vibgrate scan and what the output means.
Luke GeavesEvery codebase ages. Dependencies fall behind, runtimes approach end-of-life, and frameworks ship breaking changes that nobody applies. This silent accumulation of upgrade debt — what we call upgrade drift — is one of the most underestimated risks in modern engineering. Here's what it is, why it matters, and how to measure it.
Peter ChapmanOWASP's refreshed guidance on software supply chain security puts outdated components and transitive dependency risks front and centre. Here is what engineering teams need to know — and do — to stay ahead of the curve heading into 2026.
Luke Geaves