#softwaresecurity
Live, measured metrics for the hashtag #softwaresecurity from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #softwaresecurity
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 · fosstodon.org (Mastodon public tags API) · fetched 2026-09-14 20:09 UTC1 uses by 1 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · fosstodon.org (Mastodon public search API) · fetched 2026-09-14 20:09 UTCNo related tags with measured usage found for #softwaresecurity.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-09-14 20:09 UTCEverything below is measured over the latest 40 public posts (spanning ~3825 hours).
Posting hours (UTC) — busiest: 12:00
Languages: English (36) · German (3) · French (1)
Avg boosts / post: 0.8
Top of the latest posts
One small change can make a big difference in software supply chain security. PyPI has introduced a new safeguard that rejects uploads of new files to package releases older than 14 days. This helps prevent attackers who compromise a mainta
EU Cyber Resilience Act Spurs Rush to Track Software Vulnerabilities Get ready for a new era of cyber transparency: by September 11, 2026, EU manufacturers with digital products must report vulnerabilities to ENISA within 24 hours of discov
😳 Ah, yes, because who better to endorse software security than someone advocating for the erasure of entire communities? 🛡️🙄 Clearly, #1Password is looking to diversify its user base with individuals of questionable moral fiber. 🧠💥 ht
#softwaresecurity across platforms
every network with a public tag surfaceFollow #softwaresecurity 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/softwaresecurity