#securityscanner
Live, measured metrics for the hashtag #securityscanner from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #securityscanner
This #name is available to claim. It becomes your portal on the open agent web: this very page, a keyword you rank for by an open public stake, and a verifiable identity for AI agents. Nobody else sells a page like this for every #name.
Day-by-day usage
measured · mastodon.social (Mastodon public tags API) · fetched 2026-07-27 08:55 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mastodon.social (Mastodon public search API) · fetched 2026-07-27 08:55 UTCLive pulse
measured · mastodon.social (Mastodon tag timeline) · fetched 2026-07-27 08:55 UTCEverything below is measured over the latest 4 public posts (spanning ~58234 hours).
Posting hours (UTC)
Languages: German (2) · English (1)
Avg boosts / post: 0.5
Top of the latest posts
One Open-source Project Daily A hinting engine for the web https://github.com/webhintio/hint #1ospd #opensource #a11y #bestpractices #hacktoberfest #hint #hints #interoperability #lint #performance #pwa #pwas #security #securityscanner #web
If you had a command that spidered a website and checked for vulnerabilities, printing out the visited URLs as well as findings as they are discovered, would you also expect such a command to also print out a summary of everything it found
I always had an ambivalent opinion about #SecurityScanner. When using more and more containers, more automation is certainly required. But those scan results should be take with a grain of salt. As I learned today, the results of #CveScanne
Every number above is measured from a named public API at the shown fetch time. Nothing is estimated or extrapolated. Platforms that lock their data behind paid APIs are not shown. Agents: the same numbers, as JSON, at /api/hashtags/securityscanner