Compliance cases

These are the 7,246 inputs a submission must answer. A conforming implementation returns true for the 2,791 valid ones and false for the 4,455 invalid ones. You can run the suite without reading it, or open any case to see its input and where its first ill-formed byte is.

Well-formed means Table 3-7 of the Unicode Standard, as RFC 3629 restates it: no overlong forms, surrogates, code points above U+10FFFF, stray continuation bytes or sequences cut short. The compliance suite combines Markus Kuhn's UTF-8 stress test, WPT's fatal TextDecoder tests, every lead byte against the edges of its allowed ranges, errors at every offset around 16-, 32- and 64-byte blocks and at the end of every length up to 130 bytes, large inputs, and seeded random text. simdutf, Python and a Table 3-7 reference agree on every answer.

Run the full compliance suite locally. Replace your-component.wasm with your compiled component. Download the suite

curl -fLo validate_utf8.comply.wasm https://calculated.world/comply/validate_utf8.wasm
npx qipok your-component.wasm --suite validate_utf8.comply.wasm
Clear

130 of 7,246 cases · 130 true · 0 false

Case Name Expected Note Size
000202 regression/single byte 65 Focused regression true 1 B
000203 regression/single byte 66 Focused regression true 1 B
000204 regression/single byte 67 Focused regression true 1 B
000205 regression/single byte 68 Focused regression true 1 B
000206 regression/single byte 69 Focused regression true 1 B
000207 regression/single byte 6A Focused regression true 1 B
000208 regression/single byte 6B Focused regression true 1 B
000209 regression/single byte 6C Focused regression true 1 B
000210 regression/single byte 6D Focused regression true 1 B
000211 regression/single byte 6E Focused regression true 1 B
000212 regression/single byte 6F Focused regression true 1 B
000213 regression/single byte 70 Focused regression true 1 B
000214 regression/single byte 71 Focused regression true 1 B
000215 regression/single byte 72 Focused regression true 1 B
000216 regression/single byte 73 Focused regression true 1 B
000217 regression/single byte 74 Focused regression true 1 B
000218 regression/single byte 75 Focused regression true 1 B
000219 regression/single byte 76 Focused regression true 1 B
000220 regression/single byte 77 Focused regression true 1 B
000221 regression/single byte 78 Focused regression true 1 B
000222 regression/single byte 79 Focused regression true 1 B
000223 regression/single byte 7A Focused regression true 1 B
000224 regression/single byte 7B Focused regression true 1 B
000225 regression/single byte 7C Focused regression true 1 B
000226 regression/single byte 7D Focused regression true 1 B
000227 regression/single byte 7E Focused regression true 1 B
000349 regression/all ASCII bytes Focused regression true 128 B
000350 regression/NUL bytes Focused regression true NUL is an ordinary ASCII byte. 1.0 KiB
000351 regression/UTF-16LE text without BOM Focused regression true UTF-16LE for 'hi' is h, NUL, i, NUL: all ASCII, so also valid UTF-8. 4 B
005314 regression/64 KiB ASCII Focused regression true 64.0 KiB

Where these rules come from

Well-formed UTF-8 is defined by Table 3-7 of the Unicode Standard, chapter 3 , which RFC 3629 restates as ABNF. Every answer is agreed by simdutf 9.4.0, Python’s strict codec and a direct reading of the table; the suite’s own tests add Node.js’s buffer.isUtf8 and a fatal TextDecoder.