What it looks like
A flat two-part badge: an OLYDI label beside a muted scanned value. Monochrome, no gradient, no shadow. The live image is served at /api/badge.
GET https://olydi.com/api/badge → image/svg+xml
README badge
A monochrome mark that says this repo runs OLYDI.
The OLYDI badge is a small, neutral SVG you can drop into your README or a pull-request template. It renders the same rollup-only state every time — it never publishes a finding count, a severity, or a dollar figure. It tells visitors your scan is in the loop and points them to where they can run their own.
Markdown for your README
Copy this into your README. The badge links back to olydi.com so readers can scan their own repo.
[](https://olydi.com)
HTML, if you prefer
For docs sites or PR templates that render raw HTML rather than Markdown.
<a href="https://olydi.com"><img src="https://olydi.com/api/badge" alt="OLYDI · scanned" /></a>
Share it as a guest
The badge needs no account and no API key — it is a static image. Drop it in an open-source README, an internal wiki, or a slide before you have an OLYDI workspace. When a teammate clicks through, they land on the free scan path and can see real findings on their own pull request first.
Honest about what it is
The badge is a brand and demand-generation mark, not a security attestation. It does not certify that a repository is clean, that a scan ran on a given commit, or that any finding was fixed. The proof of a scan lives in the pull-request checks, the SARIF in the GitHub Security tab, and the evidence record — never in the badge itself. If you need an attestation, that is a security-leadership conversation, and the handoff is valty.ai.