Repository navigation
Releases
Release 0.64.9
Fixed
Improve repair performance for long and malformed LLM outputs when they contain:
- Long or truncated strings.
- Arrays of strings with unescaped inner quotes.
- Many brackets or braces inside strings.
- Table rows following a missing row bracket.
- Long prose or numbered lines before the JSON.
Thanks to @deadstrobe5 for identifying these bottlenecks and proposing fixes in #252
Support this project
json_repair is maintained as a side project and stays free for everyone.
If it saves you debugging time, helps you handle LLM-generated JSON, or is part of your production workflow, please consider:
- starring the repository to help more developers find it
- sharing it with teams working with unreliable JSON output
- sponsoring the project here: https://github.com/sponsors/mangiucugna
Sponsorship helps justify the time spent fixing edge cases, improving performance, and keeping the library reliable.
Release 0.64.8
Fixed
- Fix #251, dangling exponents such as 1e, 1e+, and 1e- being returned as strings or producing extra array elements. In standard mode, they now repair to the numeric prefix; strict mode raises an error
- Fix #250, numbers followed by consecutive commas in objects, preserving the number and subsequent fields. Strict mode rejects the malformed input
Support this project
json_repair is maintained as a side project and stays free for everyone.
If it saves you debugging time, helps you handle LLM-generated JSON, or is part of your production workflow, please consider:
- starring the repository to help more developers find it
- sharing it with teams working with unreliable JSON output
- sponsoring the project here: https://github.com/sponsors/mangiucugna
Sponsorship helps justify the time spent fixing edge cases, improving performance, and keeping the library reliable.
Release 0.64.6
Fixed
- Support reading non-seekable text streams with
load(). - Preserve valid top-level empty strings as JSON text.
- Fix file-wrapper slicing to follow Python string slicing rules.
- Preserve literal values in schema keywords such as
constandenum. - Raise a clear
ValueErrorfor invalid schema definitions, including invalid legacy tuple schema keywords.
Support this project
json_repair is maintained as a side project and stays free for everyone.
If it saves you debugging time, helps you handle LLM-generated JSON, or is part of your production workflow, please consider:
- starring the repository to help more developers find it
- sharing it with teams working with unreliable JSON output
- sponsoring the project here: https://github.com/sponsors/mangiucugna
Sponsorship helps justify the time spent fixing edge cases, improving performance, and keeping the library reliable.
Release 0.64.5
Fixed
- Fix #247, fix an issue with backslashes at the end of a string
Support this project
json_repair is maintained as a side project and stays free for everyone.
If it saves you debugging time, helps you handle LLM-generated JSON, or is part of your production workflow, please consider:
- starring the repository to help more developers find it
- sharing it with teams working with unreliable JSON output
- sponsoring the project here: https://github.com/sponsors/mangiucugna
Sponsorship helps justify the time spent fixing edge cases, improving performance, and keeping the library reliable.
Release 0.64.4
Fixed
- Fix #245, fix a performance issue when managing long escaped strings. Thanks to @den-run-ai for the proposed fix.
Support this project
json_repair is maintained as a side project and stays free for everyone.
If it saves you debugging time, helps you handle LLM-generated JSON, or is part of your production workflow, please consider:
- starring the repository to help more developers find it
- sharing it with teams working with unreliable JSON output
- sponsoring the project here: https://github.com/sponsors/mangiucugna
Sponsorship helps justify the time spent fixing edge cases, improving performance, and keeping the library reliable.
Release 0.64.3
Fixed
- Fix #240, fix comment parsing-skipping behavior in array and object context
Support this project
json_repair is maintained as a side project and stays free for everyone.
If it saves you debugging time, helps you handle LLM-generated JSON, or is part of your production workflow, please consider:
- starring the repository to help more developers find it
- sharing it with teams working with unreliable JSON output
- sponsoring the project here: https://github.com/sponsors/mangiucugna
Sponsorship helps justify the time spent fixing edge cases, improving performance, and keeping the library reliable.
Release 0.64.2
Fixed
- Fix #239, add support for more Pydantic v2 standard
Support this project
json_repair is maintained as a side project and stays free for everyone.
If it saves you debugging time, helps you handle LLM-generated JSON, or is part of your production workflow, please consider:
- starring the repository to help more developers find it
- sharing it with teams working with unreliable JSON output
- sponsoring the project here: https://github.com/sponsors/mangiucugna
Sponsorship helps justify the time spent fixing edge cases, improving performance, and keeping the library reliable.
Release 0.64.1
Fixed
- Fix #237, add support for more Pydantic standard
Support this project
json_repair is maintained as a side project and stays free for everyone.
If it saves you debugging time, helps you handle LLM-generated JSON, or is part of your production workflow, please consider:
- starring the repository to help more developers find it
- sharing it with teams working with unreliable JSON output
- sponsoring the project here: https://github.com/sponsors/mangiucugna
Sponsorship helps justify the time spent fixing edge cases, improving performance, and keeping the library reliable.
Release 0.64.0
Added
- Fix #233, recover a missing opening { when a quoted key, colon, and closing } indicate an object, and inserting { makes the entire input valid JSON.
Support this project
json_repair is maintained as a side project and stays free for everyone.
If it saves you debugging time, helps you handle LLM-generated JSON, or is part of your production workflow, please consider:
- starring the repository to help more developers find it
- sharing it with teams working with unreliable JSON output
- sponsoring the project here: https://github.com/sponsors/mangiucugna
Sponsorship helps justify the time spent fixing edge cases, improving performance, and keeping the library reliable.
Release 0.63.5
Fixed
Support this project
json_repair is maintained as a side project and stays free for everyone.
If it saves you debugging time, helps you handle LLM-generated JSON, or is part of your production workflow, please consider:
- starring the repository to help more developers find it
- sharing it with teams working with unreliable JSON output
- sponsoring the project here: https://github.com/sponsors/mangiucugna
Sponsorship helps justify the time spent fixing edge cases, improving performance, and keeping the library reliable.