Meet DriftRisk™
Three numbers, one decision. Your DriftScore tells you how far behind you are. Your RiskScore tells you how exposed you are. DriftRisk™ tells you how hard to act — a single 0–100 headline, always shown next to the two scores it comes from.
One number, because leaders triage in ones
DriftScore and RiskScore live on different axes on purpose — a stale-but-safe stack and a current-but-exploited stack are different problems. But a leader triaging twenty services doesn't want to combine two numbers twenty times. DriftRisk does that combination in a consistent, published way, so one glance ranks what needs attention.
| DriftScore | RiskScore | DriftRisk™ | What it means |
|---|---|---|---|
| low | low | low | current and safe — maintain |
| low | high | high | current stack, active exploit — patch now |
| high | low | moderate | falling behind, no exploit yet — plan the upgrade |
| high | high | high | stale and exploitable — escalate |
The rule that makes it trustworthy
A stack can be perfectly current and still be on fire because one dependency has an actively-exploited vulnerability. A naive blend would average that emergency down to a calm “moderate” because the drift is low. DriftRisk applies an override: when your RiskScore is critical, DriftRisk is high regardless of how current you are. A live security emergency never reads green because upgrade debt happens to be low.
Open algorithm, protected name
DriftRisk™ is a trademark of Vibgrate — but the algorithm is open source and published in full, including the exact blend and the override. The protection is on the name, not the method. DriftScore and RiskScore are not trademarked.
See your three scores in about a minute
Install the Vibgrate CLI and run your first scan — no account required, no source code uploaded.