#gitlost
Live, measured metrics for the hashtag #gitlost from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #gitlost
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 10:03 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 10:03 UTCNo related tags with measured usage found for #gitlost.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 10:03 UTCEverything below is measured over the latest 8 public posts (spanning ~52 hours).
Posting hours (UTC)
Languages: English (7) · French (1)
Avg boosts / post: 3.6
Top of the latest posts
#AI: GitHub AI allows unauthenticated attackers to pull data from private repositories by posting a crafted GitHub Issue in a public repository. Noma Security research dubbed this prompt injection attack #GitLost: #AISecurity 👇 https://nom
https://winbuzzer.com/2026/07/09/gitlost-prompt-injection-can-leak-github-private-repos-xcxwbn/ A look at GitLost, the GitHub Agentic Workflows prompt-injection case where public issue text, private repo access, and public comments collide.
Yet another prompt injection attack: GitLost GitHub's agentic AI is leaking information form private repositories. I like the way Noma Security puts it: Prompt injections seem to be the modern version of SQL injections. https://noma.securit
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/gitlost