#CWEs
Live, measured metrics for the hashtag #CWEs from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #cwes
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-07-28 05:10 UTC0 uses by 0 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-07-28 05:10 UTCLive pulse
measured · mastodon.social (Mastodon tag timeline) · fetched 2026-07-28 05:10 UTCEverything below is measured over the latest 7 public posts (spanning ~22582 hours).
Posting hours (UTC)
Languages: English (5) · Chinese (1) · Russian (1)
Avg boosts / post: 0.3
Top of the latest posts
Want to know the top ten #CWEs in CISA’s “Known Exploited Vulnerabilities (#KEV) Catalog”? The “2023 CWE Top 10 KEV Weaknesses” list is now available on the CWE website! List - https://cwe.mitre.org/top25/archive/2023/2023_kev_list.html Key
#HTB #CWES 感覺可以開個 My Road To CWES 串文紀錄一下
RE: https://mastodon.social/@CVE_Program/116885522589317216 CNAs are regularly including #CWEs in their #CVE Records to provide enhanced #vulnerability data for downstream consumers
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/cwes