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

11 of 7,246 cases · 2 true · 9 false

Case Name Expected Note Size
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
001890 regression/UTF-16LE BOM Focused regression false 6 B
001891 regression/UTF-16BE BOM Focused regression false 6 B
001892 regression/latin-1 text Focused regression false 'café naïve' in latin-1, not UTF-8. 10 B
001893 regression/cp1252 text Focused regression false '“smart quotes” – €5' in cp1252, not UTF-8. 19 B
001894 regression/cp1251 text Focused regression false 'Привет' in cp1251, not UTF-8. 6 B
001895 regression/shift_jis text Focused regression false 'こんにちは' in shift_jis, not UTF-8. 10 B
001896 regression/gb18030 text Focused regression false '你好' in gb18030, not UTF-8. 4 B
001897 regression/euc-kr text Focused regression false '안녕하세요' in euc-kr, not UTF-8. 10 B
001898 regression/iso8859-7 text Focused regression false 'Γειά' in iso8859-7, not UTF-8. 4 B
001899 regression/double-encoded UTF-8 Focused regression true Mojibake: UTF-8 bytes read as Latin-1 and encoded again are still valid. 7 B

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.