Documented case · 2026
Nunezchef
Flagged Apr 7, 2026
Secondary source
The details here rest on another site's summary of the case, not on the account holder's own post.
Known only from a secondary source: a nine-month-old account (created July 5, 2025) with 16 public repos and no followers, flagged in the pattern this explorer keeps meeting, the API answered for the account (gh api user returned 200) while the public profile returned 404. The flag followed AI-assisted commit velocity through Claude Code, per the source. His own primary post was not located in research, so this entry is graded secondary and claims nothing beyond the summary.
The record
- Suspended or flagged
- Flagged April 7, 2026
- Posted
- Known from a recovery-guide fixture file, 2026
- Ticket / discussion
- Appeal filed; no number published
- Suspected trigger
- AI-assisted commit velocity via Claude Code (per the secondary source)
- Human reply from GitHub
- Not stated
- How it ended
- Unknown; an appeal was filed
- Duration
- Not stated
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
Secondary: a recovery-guide fixture file in the beck repo describing the case; his own post was not located.
Secondary source only; no primary post located.
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.