A live DriftScore for your README
Run a scan, enable the public badge, and drop one line into your README. The badge updates itself after every scan — no manual edits, no stale numbers.
Add it to your README
Replace <owner> and <repo> with your GitHub owner and repository name.
[](https://dash.vibgrate.com/badges/driftscore/<owner>/<repo>)
<a href="https://dash.vibgrate.com/badges/driftscore/<owner>/<repo>"> <img src="https://badges.vibgrate.com/<owner>/<repo>" alt="Vibgrate DriftScore" /> </a>
For a specific branch, add to the badge image URL.
Live example
This badge is pulled live from badges.vibgrate.com for vibgrate/cli — whatever it shows is the real, current state of that endpoint, not a mockup.
Four badges, one URL scheme
DriftScore
A 0–100 score of how closely your codebase matches its intended architecture and dependency posture.
badges.vibgrate.com/vibgrate/cliCVEs
The number of known CVEs affecting dependencies in your repository from the latest Vibgrate SCA scan.
badges.vibgrate.com/cve/vibgrate/cliRiskScore
A 0–100 security & business-risk score (higher = more risk) fusing known-exploited (CISA KEV) and likely-exploited (EPSS) vulnerabilities, end-of-life runtimes, and business criticality.
badges.vibgrate.com/riskscore/vibgrate/cliDriftRisk™
A 0–100 headline (higher = more pressure to act) that blends DriftScore (maintainability) and RiskScore (security), with an override so an actively-exploited vulnerability is never washed out by a current stack.
badges.vibgrate.com/driftrisk/vibgrate/cliHow verification works
Anyone can technically embed any badge image on any page — that's true of every badge service, not just this one. What a badge URL can't do here is point at a repository someone else typed in: each URL names exactly one repository, and clicking a badge always takes you to a page that states plainly which repository it represents, with a link to verify on GitHub. If a badge's context doesn't match what that page says, that's the signal something's wrong.
First badge for a repo we haven't scanned yet?
A DriftScore badge for a public GitHub repository Vibgrate hasn't scanned before shows a brief scanning… state on its first request while a scan runs, then resolves to a real score on the next request — usually within seconds. No account or setup needed for this to happen; it only applies to DriftScore on public repositories.
Get your own badge
Install the Vibgrate CLI, run a scan, then enable the public badge for your repository in Vibgrate Cloud.