#devsec

Live, measured metrics for the hashtag #devsec from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.

hashtag.org network · sponsored

Own #devsec

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.

$520.70/ year · 6-character #name
Claim #devsec — $520.70/yr→Buy on hashtag.space (web3)
card via hashtag.org · tokens via hashtag.space
0
Uses / 7 days
Mastodon
0
Accounts / 7 days
Mastodon
40
Recent posts
Mastodon
~0/hr
Recent pace
Mastodon · last 40
0.1
Avg reactions / post
Mastodon · last 40
—
Reddit posts / month
Reddit search
—
Open-web mentions
hashtag.org Firehose

Day-by-day usage

measured · mastodon.online (Mastodon public tags API) · fetched 2026-11-02 12:15 UTC
0
10-27
0
10-28
0
10-29
0
10-30
0
10-31
0
11-01
0
11-02

0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.

Related hashtags

measured · mastodon.online (Mastodon public search API) · fetched 2026-11-02 12:15 UTC
#devsecops
40 uses · 33 accounts / 7d
#devsecurity
2 uses · 2 accounts / 7d
#devsecops_и_devops
0 uses · 0 accounts / 7d
#devsecopsday
0 uses · 0 accounts / 7d
#devsecops2026
0 uses · 0 accounts / 7d
#devsecopsguide
0 uses · 0 accounts / 7d
#devsecopsimplementation
0 uses · 0 accounts / 7d
#devsecopspipeline
0 uses · 0 accounts / 7d
#devsecopsroi
0 uses · 0 accounts / 7d
#devsecopsculture
0 uses · 0 accounts / 7d
#devsecopsmaturitymodel
0 uses · 0 accounts / 7d
#devsecopspodcast
0 uses · 0 accounts / 7d

Live pulse

measured · mastodon.online (Mastodon tag timeline) · fetched 2026-11-02 12:15 UTC

Everything below is measured over the latest 40 public posts (spanning ~22633 hours).

Posting hours (UTC) — busiest: 10:00

00:0012:0023:00

Languages: English (31) · German (6) · Portuguese (2)

Avg boosts / post: 0.6

Top of the latest posts

  • @zendis #DevSecOps by Zendis, jedenfalls die #DevSec Seite Das ist genau der richtige Weg!

    Thomas Fricke (he/his)@[email protected]♥ 2↻ 02025-04-10 12:44 UTCView post →

  • 🔐 Coder — 6 CVEs, versions 2.3–2.35 CVE-2026-111927 (7.7): hostname bypass via SQL SIMILAR TO prefix match → application_connect API key theft. CVE-2026-111928 (5.5): RBAC skips org membership check → removed users keep access. CVE-2026-11

    threataft@[email protected]♥ 0↻ 12026-10-19 15:58 UTCView post →

  • Am 2. Oktober 2026 benachrichtigte mich das Team von Patchstack über eine Sicherheitslücke in Form Block 1.8.1 und niedriger, die es einem Angreifer ermöglichte, Cross-Site-Scripting (XSS) auf der Seite der Formularübermittlungen im Backend

    Epiphyt@[email protected]♥ 0↻ 02026-10-13 14:00 UTCView post →

#devsec across platforms

every network with a public tag surface

Follow #devsec 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.

X (Twitter) ↗Instagram ↗TikTok ↗Facebook ↗LinkedIn ↗YouTube ↗Threads ↗Bluesky ↗Mastodon ↗Reddit ↗Pinterest ↗Tumblr ↗

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/devsec