Then one day: 404.

Unlike Wikipedia’s built-in moderation, a GitHub wiki often has . If they go bad, get hacked, or sell out, there’s no emergency button.

A GitHub wiki is not a set-it-and-forget-it knowledge base. It’s a Git repo with an attractive UI wrapper—and like any repo, it can be nuked, poisoned, or kidnapped.

Welcome to the dark side of community wikis.

P.S. If your project’s wiki just went dark, check the repo’s network graph. Someone probably forked it before the corruption. That fork might be your new bible.

They’re just separate Git repos ( repo.wiki.git ). That’s powerful—you can clone, fork, and audit history. But it also means anyone with write access to the main repo (or wiki-specific perms) can rewrite history, delete pages, or push propaganda.

Here’s a short, punchy blog post draft on the “corrupt wiki GitHub” phenomenon—assuming you mean the recurring drama where GitHub-hosted wikis (often for game modding, emulation, or open-source projects) get locked, deleted, or manipulated due to bad actors, DMCA abuse, or internal power struggles. When the Wiki Goes Rogue: Corruption, Clout, and Code on GitHub