#SoftwareSupplyChainSecurity
Live, measured metrics for the hashtag #SoftwareSupplyChainSecurity from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #softwaresupplychainsecurity
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-10-27 00:45 UTC2 uses by 2 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-10-27 00:45 UTCNo related tags with measured usage found for #softwaresupplychainsecurity.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-10-27 00:45 UTCEverything below is measured over the latest 40 public posts (spanning ~5533 hours).
Posting hours (UTC) — busiest: 07:00
Languages: English (38) · German (2)
Avg boosts / post: 0.8
Top of the latest posts
#Rust supply-chain attack: the popular `arrayref` crate (245mln downloads) was compromised to run a remote payload at build time. Simply running `cargo build` was enough to get infected: #SoftwareSupplyChainSecurity 👇 https://www.stepsecur
Docker OIDC connections for GitHub Actions available for Docker Orgs #Docker #Products #DockerHub #Githubactions #Oidcconnections #Security #Softwaresupplychainsecurity https://www.docker.com/blog/docker-oidc-connections-for-github-actions-
RE: https://mastodon.social/@asfaload/117506063307193577 Here's a small improvement that required some significant refactoring. It's similar to a TOCTTOU: the signature of a release was provided in a second step, leaving a small opportunity
#softwaresupplychainsecurity across platforms
every network with a public tag surfaceFollow #softwaresupplychainsecurity 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/softwaresupplychainsecurity