Documented case · 2026
Manav Arya Singh (@Manavarya09), AI engineer, Dubai
Flagged Jun 25, 2026; restored about Aug 22, 2026
Verified primary source
The account holder's own post, discussion or thread was opened and read in full for this entry.
Flagged by automated abuse detection on June 25, 2026. His public repos vanished, his profile returned 404 when logged out, and his OAuth logins broke, which took his Vercel and Render deployments down with them. One hidden repo, design-extract, had about 3,400 stars and active GitHub Sponsors; he has 193 public repos in total. He did what almost no one else in this explorer could do: he exported his own security log and counted. Of 19,173 log rows, 13,349 were OAuth token-lifecycle events, and 12,481 of those, 93.5 percent, came from GitHub's own Copilot integrations (PR Reviewer 8,921; Chat App 2,782; SWE Agent 778), against 75 from Claude. The reason codes were expired (2,535) and max_for_app (1,903), an app hitting its own token ceiling and churning. He cites the public VS Code issue where an engineer confirmed a genuine Copilot token-lifecycle bug, and notes another user on that thread had their account fully disabled by it. The harm is countable in his post: design-extract gained 369 stars in June before the flag, zero stars in July while hidden, then 164, 182, and 189 stars on August 25, 26, and 27 after restoration. Sponsorship income was lost for two months, internship work was blocked, and [email protected] bounced, the same bounce recorded in my own case above. There is no phone support, Sponsors has no separate channel, and posting at GitHub on X did nothing.
The record
- Suspended or flagged
- Flagged June 25, 2026
- Posted
- His blog, August 22, 2026
- Ticket / discussion
- Ticket #4511409, filed day 0, resolved day 58
- Suspected trigger
- His inference, backed by his own security-log export: high commit granularity from AI-assisted work, plus Copilot OAuth token churn, read as bot behaviour. GitHub never told him which signal tripped the flag
- Human reply from GitHub
- Eventually: a formal escalation on day 47 was answered in about 40 minutes, after 31 days of silence. Follow-ups on days 11, 19, 29, 42, and 56 mostly went into the quiet
- How it ended
- Restored on day 58 with a three-line reinstatement message: the activity had been highlighted for manual review, the restrictions were cleared, full access restored. No signal, threshold, or reason was ever named
- Duration
- 1 to 3 months
Suspected triggers are the account holder’s inference, never GitHub-confirmed, unless the record above says GitHub stated or confirmed it. A suspension does not by itself prove GitHub made a mistake.
Sources
First-hand post by Manav Arya Singh, manavaryasingh.com, August 22, 2026; opened and checked November 17, 2026.
The 93.5 percent figure is from his own security-log export, published in his post; GitHub has not confirmed it.
This entry is one of 66 in What Kind of Life Does a Flag Preserve?, a documented account of GitHub suspending a fourteen-year-old developer account and the same pattern repeating across the industry. If the same thing has happened to you, the article’s eight-step playbook is built from what actually moved these cases.