#codeanalysis
Live, measured metrics for the hashtag #codeanalysis from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #codeanalysis
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-11-10 14:58 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-11-10 14:58 UTCNo related tags with measured usage found for #codeanalysis.
Live pulse
measured · mastodon.social (Mastodon tag timeline) · fetched 2026-11-10 14:58 UTCEverything below is measured over the latest 40 public posts (spanning ~7907 hours).
Posting hours (UTC) — busiest: 18:00
Languages: English (31) · Korean (3) · Russian (2) · German (2)
Avg boosts / post: 0.3
Top of the latest posts
Today I found a helper TUI for coding Rust 🦀 🛠️ ploke — Graph-native Rust code analysis in your terminal. 🧠 Understand your project with a fully queryable code graph & context-aware assistant. 🦀 Written in Rust & built with @ratatui_rs
Slopscore "slopscore is a tool for scanning git repositories for signs of LLM tool use. detections are found through various heuristics, providing a good starting point for somemany to understand the effects of AI on a software project." Us
Thanks for this, @JessTheUnstill! Guess I can brag about my static code analyzer: it scans a 42K LOC Java codebase in 4 seconds, with over 30 rules enabled. https://codeberg.org/bannmann/mandor Here's the story: Working solo on that Java co
#codeanalysis across platforms
every network with a public tag surfaceFollow #codeanalysis 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/codeanalysis