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

1,161 of 7,246 cases · 619 true · 542 false

Case Name Expected Note Size
005280 regression/E2 82 ending 128 bytes Focused regression false 128 B
005281 regression/E2 ending 128 bytes Focused regression false 128 B
005287 regression/U+20AC ending 128 bytes Focused regression true 128 B
005289 regression/E2 82 ending 129 bytes Focused regression false 129 B
005290 regression/E2 ending 129 bytes Focused regression false 129 B
005296 regression/U+20AC ending 129 bytes Focused regression true 129 B
005299 regression/E2 82 ending 130 bytes Focused regression false 130 B
005300 regression/E2 ending 130 bytes Focused regression false 130 B
005306 regression/U+20AC ending 130 bytes Focused regression true 130 B
005309 regression/every 3-byte scalar Focused regression true 180.0 KiB
005317 regression/64 KiB CJK 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.