#rubysec
Live, measured metrics for the hashtag #rubysec from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #rubysec
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-07-27 11:11 UTC0 uses by 0 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-07-27 11:11 UTCNo related tags with measured usage found for #rubysec.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 11:11 UTCEverything below is measured over the latest 40 public posts (spanning ~24631 hours).
Posting hours (UTC) — busiest: 18:00
Languages: English (40)
Avg boosts / post: 0.9
Top of the latest posts
Just released bundler-audit 0.9.3, which officially adds support for Ruby 3.4, 3.5, 4.0, and Bundler 4.x. https://github.com/rubysec/bundler-audit/releases/tag/v0.9.3 https://github.com/rubysec/bundler-audit#readme #ruby #bundler #rubysec #
💣 Is your #Ruby app vulnerable to known CVEs? Is it safe in production? Is it ready for a #SOC2 audit? If you don’t know, you need a security audit. Find out how many vulnerabilities are present in your code and dependencies. Let's talk! h
PSA: supply chain attacks (aka forking popular gems, changing the name slightly, and adding malicious code) are starting to show up on https://rubygems.org more often. Be cautious when adding a new gem to your project. Check who the author
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/rubysec