Transparency badge

The evidence, on your own page

One image, served from Evidesa: the overall score band for a mint and the coverage ratio behind it. It links to the full Evidence Dossier so a reader can check the evidence rather than take the number on trust. It is not a certification, a seal, or an audit mark, and there is no version of it that says a token is safe.

What it renders

Evidesa evidence badge for EXAMPLE: overall score 71 of 100, High band.Overall score 71 of 100 in the High band, from 4 of 5 implemented categories evaluated with 1 evidence gap — derived. A band is a score range, not a verdict, and unavailable evidence is not evidence of low risk.EVIDESAEXAMPLE71HIGH4/5 EVALUATED · 1 GAPPOINT-IN-TIME EVIDENCE · NOT A VERDICT
Example only — illustrative scores, not real reports, and labelled EXAMPLE where a real badge carries the mint. Left to right: the mark and the score in solid digits, the joint, then the band word over the coverage ratio.
Evidesa evidence badge for EXAMPLE: overall score 91 of 100, Critical band.Overall score 91 of 100 in the Critical band, from 5 of 5 implemented categories evaluated with 0 evidence gaps — derived. A band is a score range, not a verdict, and unavailable evidence is not evidence of low risk.EVIDESAEXAMPLE91CRITICAL5/5 EVALUATED · 0 GAPSPOINT-IN-TIME EVIDENCE · NOT A VERDICT
Severity is the joint. Its lit face takes the hue and its width steps 1 · 2 · 4 · 8px with the band, and at Critical the band slab also sits 2px out of alignment — a silhouette event that survives greyscale, a thumbnail and heavy compression.
Evidesa evidence badge: no report — evidence not retrieved.A report could not be produced from the currently available provider responses, so this badge states nothing about the token — unestablished.EVIDESAEXAMPLE—UNESTABLISHEDEVIDENCE NOT RETRIEVEDPOINT-IN-TIME EVIDENCE · NOT A VERDICT
When no report can be produced, the number is cut out of the material and the band word is set as a void. The badge makes no claim about the token.

The digits are always solid. The report page cuts coverage into the numeral itself, but a hollowed numeral is unreadable once an embedder scales the image down, so at badge scale coverage is carried by the ratio line instead — and it is never optional. Every kerf in the badge is an explicit plate fill rather than transparency, so a white page behind it cannot quietly close a gap.

Embed it

Replace MINT_ADDRESS with the mint address, in both places. The badge is a plain image — no script, no iframe, no cookie, and nothing is read from the page it sits on.

<a href="https://www.evidesa.com/report/MINT_ADDRESS">
  <img src="https://www.evidesa.com/badge/MINT_ADDRESS"
       width="260" height="100"
       alt="Evidesa evidence badge for MINT_ADDRESS">
</a>

Intrinsic size 260×100. Scale it with the width and height attributes together; do not crop it, recolour it, or place it on a surface that removes its plate — the plate is the void the badge measures gaps against.

What it does not claim

  • that the token is safe, unsafe, audited, verified, or endorsed — none of those words can appear in the badge
  • a verdict — the band word is a score range, and the score is the maximum of the implemented categories, not an average
  • completeness — the coverage ratio is rendered every time, so a number never appears without the evidence behind it
  • currency — the badge is a point-in-time read that can be up to 90 seconds old, and the underlying evidence changes

Unavailable evidence is not evidence of low risk. See the limitations and the methodology.

Responses

Every response is an SVG, so the badge never renders as a broken image — but the status code tells an automated embedder the truth, and only a produced report is cacheable.

200A report was produced for this mint.

Score in solid digits, band word, severity joint, and the coverage ratio behind the score.

400The path segment is not a valid Solana mint address.

The neutral badge: a void where the number goes, UNESTABLISHED, and MINT ADDRESS NOT VALID. No token is named.

429A request or capacity budget was reached for the requesting network.

The neutral badge with the limit as its reason, and a Retry-After header. Never cached.

503The RPC endpoint is unconfigured, or evidence could not be retrieved.

The neutral badge with the reason. An unavailable provider is not a low-risk result.

A produced badge is cacheable for 90 seconds, which is the report cache lifetime — it cannot be fresher than the evidence behind it. Neutral badges are never cached. Badge requests are metered by the same budgets as the report page, so a high-traffic page shares one report generation rather than triggering one per visitor.