#opensourcesecurity
Live, measured metrics for the hashtag #opensourcesecurity from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #opensourcesecurity
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-09-15 06:00 UTC4 uses by 4 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-09-15 06:00 UTCNo related tags with measured usage found for #opensourcesecurity.
Live pulse
measured · mastodon.social (Mastodon tag timeline) · fetched 2026-09-15 06:00 UTCEverything below is measured over the latest 40 public posts (spanning ~1614 hours).
Posting hours (UTC) — busiest: 12:00
Languages: English (35) · Portuguese (1) · Swedish (1) · German (1) · French (1)
Avg boosts / post: 1.8
Top of the latest posts
A maintainer who receives a security vulnerability report might feel overwhelmed, anxious, and uncertain about what steps should be taken. If this applies to you, our Ecosystem Security Team published a guide today on exactly what to do nex
I got to chat with @mairin about Red Hat's Project Lightwell on #OpenSourceSecurity It's going to be interesting to figure out how everyone will start interacting with open source projects. This is something Red Hat is pretty good at alread
Wednesday night I'll be speaking at the NYC Open Source Security User Group meetup. If your release pipeline still has stored API tokens in it, come find out how to delete them for good. Wed Aug 26, 6-8 PM, pizza at 6, talk at 6:30 Amazon o
#opensourcesecurity across platforms
every network with a public tag surfaceFollow #opensourcesecurity straight to each platform’s own tag page. Where a platform publishes open data we measure it above; the rest lock their numbers behind paid APIs, so we link rather than guess.
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/opensourcesecurity