Tool ↔ standards dataset

Quick answer

14 tools mapped to the 13 published standards that define their behaviour — RFCs, NIST FIPS and IANA registries — each linked to the defining document. Free to reuse with attribution (CC BY 4.0).

14

tools citing a standard

13

distinct standards cited

2026-07-30

living registry last checked

“Trust me, my formatter is correct” is not a checkable claim, and almost no online dev-tool site cites anything at all. Each row below names the document that actually defines the behaviour, so you can verify the tool against the spec instead of taking our word for it.

Download JSON

The mapping

ToolDefining standard
ASCII TableIANA Character Sets registry (ANSI_X3.4-1968)
BASE64RFC 4648 — The Base16, Base32, and Base64 Data Encodings
CSV To JSONRFC 4180 — Common Format and MIME Type for CSV Files
Hash GeneratorNIST FIPS 180-4 — Secure Hash Standard (SHS), RFC 1321 — The MD5 Message-Digest Algorithm
Http Status CodesIANA HTTP Status Code Registry
JSON DiffRFC 6902 — JavaScript Object Notation (JSON) Patch
JSON FormatterRFC 8259 — The JSON Data Interchange Format
JSON Minify OnlineRFC 8259 — The JSON Data Interchange Format
JSON To CSVRFC 4180 — Common Format and MIME Type for CSV Files
JWT DecoderRFC 7519 — JSON Web Token (JWT), RFC 7515 — JSON Web Signature (JWS)
JWT EncoderRFC 7519 — JSON Web Token (JWT), RFC 7515 — JSON Web Signature (JWS)
URL EncodeRFC 3986 §2.1 — Percent-Encoding
UUID GeneratorRFC 9562 — Universally Unique IDentifiers (UUIDs)
XML FormatterW3C XML 1.0 (Fifth Edition)

Living registries

A fixed RFC is cited once because it does not change. A registry does — theIANA HTTP Status Code Registryhas gained codes (103, 425, 451) since the original specs, so it carries a review cadence instead: last checked 2026-07-30, due again by 2027-01-26.

Licence & citation

Published under CC BY 4.0. Suggested citation:

TryDevSnip, Tool ↔ Standards Dataset, Acsaven. https://trydevsnip.com/standards-dataset/

Frequently asked questions

Why publish this?

Because "trust me, my JSON formatter is correct" is not checkable, and almost no online dev-tool site cites anything. Naming the exact document that defines each behaviour lets you verify the tool against the spec yourself instead of taking our word for it.

Is the list maintained by hand?

No — it is read out of the tool pages at build time. Add a citation to a tool and it appears here; remove one and it disappears. A separate hand-kept list would eventually claim standards the tools no longer follow, which is exactly what this dataset exists to disprove.

Why do some entries have a recheck date and others not?

Fixed documents like an RFC do not change, so they are cited once. Living registries do: the IANA HTTP Status Code Registry has gained codes (103, 425, 451) since the original specs, so it carries a review cadence — last checked 2026-07-30, due again by 2027-01-26.

Can I reuse it?

Yes — CC BY 4.0, with attribution to TryDevSnip. The standards belong to their publishing bodies; this is the mapping layer.

TryDevSnip