2shell.lol: it has been a countable number of days since the last 2Shell-named vulnerability, and this page is the counter

DAYS SINCE THE LAST 2SHELL-NAMED VULNERABILITY

SWEEPING SIGNALS…

ARRIVALS newest first, like the news: every shell, its CVEs, its date, its gap

PANEL SWEEP IN PROGRESSloading data

MISSING ONE? the board takes pull requests

Fork the repo and add your shell to data/vulns.json: name, disclosure date, CVEs, affected tech, one-line summary. The live file is right here.
Open a PR. CI checks the shape; a human merges it. Snark in the copy, facts in the fields. Membership rule: a real, publicly disclosed vulnerability whose branded name ends in Shell.
The counter resets the moment you merge. Yes. That's on you.

There is also a bot. It reads the security social firehose every six hours and opens PRs for new candidates on its own. Beat it to one and your shell arrives with your name on the ticket.

{
  "name":    "Your2Shell",
  "date":    "YYYY-MM-DD",
  "cves":    ["CVE-2026-…"],
  "tech":    "what it breaks",
  "summary": "one line, ideally funny",
  "era": "wave|classic",
  "url": "a real source",
  "added_by": "you"
}