UUID PARSING / COMPILED GOOO
Parse a UUID. See every returned field.
Inspect Google UUID Parse and the returned UUID’s String through Gooo. Parsing can fail while returning a partial UUID with correctly shaped text. Check parsed before using the returned value.
Loading the compiled UUID parser…
Compiled result
No parsing has run.
Includes captured input, original and bound UTF-16 code units, all four returned fields, and build hashes. Parser errors retain the returned UUID. This browser observation is not a native execution receipt or signed attestation.
What the parser returns
parsed reports whether the original parser error was nil. canonical_uuid is the returned UUID’s lowercase text on success and error. error preserves the original error text; it is empty on success. invalid_length preserves the original length-error classification.
The parser accepts hyphenated, raw hexadecimal, case-insensitive urn:uuid:, and 38-byte wrapped input. For 38 bytes, it examines the middle 36 bytes and permits arbitrary outer delimiters, including square brackets. This follows Parse; the separate Validate operation has different rules.
The last invalid pair 0g in raw text can leave a returned byte of ff; the same hyphenated failure leaves that byte at 00. Both calls have parsed: false. A correctly shaped returned UUID does not establish parser success.
The page calls the unchanged compiled Gooo ParseCanonical activity in a Worker after verifying WebAssembly size and SHA-256 against the build manifest. JavaScript handles input binding and transport. This Text adaptation does not expose Go’s binary UUID array, ParseBytes or full-library compatibility. Parsing does not establish uniqueness, authorization or a particular UUID version.
Waiting for the verified program manifest.
Read the bound Gooo parser · Source versions and hashes · Google UUID license · Report a problem ↗