Skip to content
Back to search

faultydata-registry

Cited real-world HTTP failure signatures you can replay against any client — 107 specimens, a GitHub Action, and an MCP server. Live at faultydata.com

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 20 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/Q-Nimbus/faultydata-registry with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/Q-Nimbus/faultydata-registry'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/q-nimbus--faultydata-registry/badge.svg)](/listings/q-nimbus--faultydata-registry)

HTML

<a href="/listings/q-nimbus--faultydata-registry"><img src="/api/listings/q-nimbus--faultydata-registry/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 80 lines
  1. # FaultyData Registry
  2. The public specimen catalog behind [faultydata.com](https://faultydata.com) —
  3. a failure-signature registry of **cited real-world outages** and classic
  4. HTTP/client failure modes, each replayable live against any HTTP client.
  5. Think Have-I-Been-Pwned, but for your HTTP stack: instead of asking "was my
  6. password leaked?", ask "does my client survive the CrowdStrike channel file,
  7. a Slowloris drip, or a 429 that actually means it?"
  8. ## The catalog
  9. `specimens/` holds one YAML file per exhibit — **107 and counting**. Every
  10. specimen has:
  11. | field | meaning |
  12. |---|---|
  13. | `id` | stable `FD-YYYY-NNN` identifier — cite this in bug reports |
  14. | `slug` | human-readable URL (`/specimen/<slug>`) |
  15. | `title`, `category`, `severity` | what it is and how bad it is |
  16. | `tests` | capability tags: `parsing`, `timeouts`, `retry-logic`, `headers`, `semantics`, `loops`, `monitoring`, `auth` |
  17. | `citation` | the real postmortem/doc this is based on — nothing here is invented |
  18. | `anatomy` | the story: what happened in production and why your client should care |
  19. | `signature` | the machine-readable fault: status, headers, body, corruption mode, delays, sequences, raw wire bytes |
  20. | `expect` | (optional) which client outcomes count as surviving |
  21. Real incidents in the catalog include CrowdStrike 2024, AWS S3 us-east-1,
  22. Meta's BGP withdrawal, Cloudbleed, the XZ backdoor, Dyn, Rogers, Southwest,
  23. CodeSpaces, SolarWinds, polyfill.io, left-pad and more — plus classic
  24. pathologies like truncated JSON, redirect loops, duplicate Content-Length
  25. and HTTP/0.9 responses.
  26. ## Replay them
  27. No signup needed for the free tier (60 req/min per IP):
  28. ```sh
  29. curl https://faultydata.com/r/crowdstrike-channel-file # one exhibit, live
  30. curl https://faultydata.com/api/specimens # the whole catalog as JSON
  31. curl -X POST https://faultydata.com/battery \
  32. -H 'content-type: application/json' -d '{"suite":"starter"}'
  33. ```
  34. Exhibits that break the connection itself (resets, raw wire responses) are
  35. served unedited on the direct line `https://faultydata.com:8443`.
  36. ## Grade a client in CI — the Action
  37. [`action.yml`](action.yml) downloads the `fd` runner, points your client at
  38. each exhibit in a suite, and the **server** computes the grade — your client
  39. can't grade its own homework.
  40. ```yaml
  41. - uses: Q-Nimbus/faultydata-registry@v1
  42. with:
  43. suite: starter # starter | transport | retry-logic | timeouts | ...
  44. name: my-http-client
  45. min-score: "80" # fail CI below this
  46. client: python3 tests/http_check.py # optional; empty = Go net/http
  47. ```
  48. The client command runs once per exhibit with `$FD_URL` set (`{url}` also
  49. works). Report what happened with `FD_OUTCOME=timeout|parse_error|...` —
  50. see [`examples/http_check.py`](examples/http_check.py) and the
  51. [runner docs](https://faultydata.com/docs#runner). The step summary gets a
  52. link to the public report card and badge.
  53. Current [leaderboard](https://faultydata.com/leaderboard): OkHttp A+, node
  54. fetch A, httpx A — and curl-with-no-flags dead last at F.
  55. ## Contributing specimens
  56. Open an issue or PR with the YAML for a real, documented incident — a
  57. postmortem link is required. The bar: it must be *cited*, *reproducible*,
  58. and *named* (`FD-YYYY-NNN`). Chaos is only funny when it's attributable.
  59. ## License
  60. MIT — the catalog facts and this repo are free; the server source is not
  61. part of this repository.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.