Skip to content

Verification Badge

Embed a live badge showing how much of your repo's context still holds.

Kontrua serves an SVG badge that publishes the verdict: how many of a repository's context claims currently resolve against its code. That is the checkable number, so it is what the badge says. Freshness - how far the context trails HEAD - is only the fallback, used when the repository has no mechanically checkable claim yet. The badge is regenerated on every request and sent with Cache-Control: no-cache, so no cache busting is required.

What the badge says

The left half always reads context. The right half is one of these:

Badge right-hand label, colour and meaning
LabelColourWhen
47/47 verifiedGreenClaims were found and every one of them resolves against the code
3 claims brokenRedAt least one claim no longer resolves. The count is the number of broken claims, singular when it is one
freshGreenFallback: nothing checkable in this repo yet, and the context matches the current state of the code
3 commits behind, or agingYellowFallback: 1 to 9 commits behind HEAD, or last refreshed at least 7 days ago. It reads "aging" when the commit lag is 0
stale · 12 behind, or staleRedFallback: 10 or more commits behind HEAD, or last refreshed at least 30 days ago. It reads "stale" alone when the commit lag is 0
not trackedGreyFallback: no context run has completed for this repository yet
An unknown repository ID returns 404 with no image, rather than a badge that reads as a state.

Embed in your README

Find your repository ID in the dashboard URL (/dashboard/repos/[repoId]) and use it below:

Markdown
![Kontrua context](https://kontrua.com/api/badge/<repoId>)
HTML
<img src="https://kontrua.com/api/badge/<repoId>" alt="Kontrua context verified" />

The endpoint needs no authentication, by design: the badge belongs in a public README. The repository ID is the capability, and the response carries the label and nothing else.

A badge without an account

Any public repository that has been audited once at /try also has a badge, addressed by owner and name rather than by repository ID. It reads the stored verdict and re-audits in the background when that verdict is more than a day old, so a README that is fetched often never triggers a download.

Markdown
[![context](https://kontrua.com/api/badge/public/<owner>/<repo>)](https://kontrua.com/verdict/<owner>/<repo>)
A repository nobody has audited yet answers with a grey not audited badge rather than an error, so the image never breaks in a README.

Ready to prove your context is true?

Connect your first repository and Kontrua tells you how much of what your docs claim is still true, before it writes anything.