Attestation badge
current canonical · v1.1.0
A visual signal that your project composes the Starlight Intelligence Protocol. Drop it in your README so adopters recognise the substrate — and so credit compounds across every node.
/badge/v1.1.0Important
The badge is not the attestation. It is a visual signal of one. Real attestation lives in your README footer per /sip-attest. Use the badge to make composition visible at a glance; use the attestation block to make it auditable.
01 / Preview
02 / Markdown
The most common shape. GitHub, GitLab, npm, and crates.io all render it identically.
markdown[](https://starlightintelligence.org/protocol)
Pin to a specific version so the badge reflects what you actually built against. The protocol uses SemVer; the badge does too.
03 / Latest
Use /badge/latest if you want the badge to always reflect the current canonical SIP version. Trades pin precision for zero maintenance.
markdown[](https://starlightintelligence.org/protocol)
04 / HTML
Sites, docs platforms, anywhere markdown isn't the substrate.
html<a href="https://starlightintelligence.org/protocol"><img src="https://starlightintelligence.org/badge/v1.1.0" alt="Built on SIP" /></a>
05 / Shields.io
For adopters who prefer the shields.io style or already standardise on it across their stack. Same meaning, different chrome.
markdown[](https://starlightintelligence.org/protocol)
06 / URL contract
/badge/v1.1.0 — explicit SemVer pin (preferred)./badge/latest — resolves to current canonical SIP version (today: v1.1.0).?theme=light — light variant for light README backgrounds (default is dark).Next
The badge is the surface. The attestation block is the substance. Read the protocol to see the full contract, then run /sip-attest against your artifact.
Built on SIP · v1.1.0· MIT