I would be careful to use this without validating and normalizing the unicode prior to passing it to this parser. Not saying that it's a bad design, but big flashing security warnings should be used so that people are aware that higher order unicode can and usually is normalized prior to JSON parsing (so that, e.g. producers that use full width quotation marks can have their json parsed correctly rather than not have the double quotes recognized) and this consumer can only handle fully normalized and validated UTF8