What it shows
A small image with the name slop.watch and a short read of the report on file for the domain. Before anyone has scanned the domain, it says unscanned.
no report on file yet
The badge states what a scan found at the time of the report and nothing more. The details are on how it reads.
Embed it
Replace example.com with your domain, then scan it once at slop.watch/scan so there is a report on file. A report's own sharing section has the same snippets with your domain already in.
Markdown, for a README
[](https://slop.watch/scan/example.com)
HTML, for your own site
<a href="https://slop.watch/scan/example.com"><img src="https://slop.watch/scan/example.com/badge.svg" alt="slop.watch scan" height="20"></a>
No tracking parameters, no script, no cookie. The link goes to the report.
Caching
- A badge with a read is cached for an hour, in browsers and at our edge. After a rescan, the new read shows within the hour.
- An
unscannedbadge is never cached, so it turns into the real one as soon as a report exists. - Image proxies keep copies of their own. GitHub serves README images through its camo proxy, which decides for itself when to fetch again.
It never fails
A badge request never starts a scan and never returns an error. An unknown or invalid domain, a database that did not answer, or more badge requests than we serve in a second: each gets the unscanned badge, with status 200, so a README never shows a broken image because of us.
What a badge is worth
A README badge carries no search-ranking value. GitHub, PyPI and similar hosts mark README links nofollow and proxy the images, so search engines do not count them as links, and the report they point to is noindex anyway. We are telling you so you need not find out.
What a badge does count as: an impression, every time someone reads the README, and a referral, every time someone clicks it to see where the read came from. That is all we claim for it.