Top AI Repos — open-source AI, indexed and scored
Top AI Repos tracks AI repositories on GitHub and answers two different questions about each one: is it moving right now, and would you bet a product on it.
Top AI Repos tracks AI repositories on GitHub and answers two different questions about each one: is it moving right now, and would you bet a product on it.
🔧 Repair JSON！Solution for JSON Anomalies from LLMs.
| Date | Stars |
|---|---|
| 2026-07-24 | 382 |
| 2026-07-25 | 381 |
| 2026-07-28 | 381 |
| 2026-07-30 | 381 |
| 2026-08-06 | 381 |
Today
— stars today
This week
— stars this week
This month
— stars this month
Momentum
0.0
growth rate 0.00%/day
<!-- Improved compatibility of back to top link: See: https://github.com/RealAlexandreAI/json-repair/pull/73 -->
<a name="readme-top"></a>
<!--
*** Thanks for checking out the Best-README-Template. If you have a suggestion
*** that would make this better, please fork the repo and create a pull request
*** or simply open an issue with the tag "enhancement".
*** Don't forget to give the project a star!
*** Thanks again! Now go create something AMAZING! :D
-->
<!-- PROJECT SHIELDS -->
<!--
*** I'm using markdown "reference style" links for readability.
*** Reference links are enclosed in brackets [ ] instead of parentheses ( ).
*** See the bottom of this document for the declaration of the reference variables
*** for contributors-url, forks-url, etc. This is an optional, concise syntax you may use.
*** https://www.markdownguide.org/basic-syntax/#reference-style-links
-->
[![Contributors][contributors-shield]][contributors-url]
[![Forks][forks-shield]][forks-url]
[![Stargazers][stars-shield]][stars-url]
[![Issues][issues-shield]][issues-url]
[![GPL License][license-shield]][license-url]
<!-- PROJECT LOGO -->
<br />
<div align="center">
<a href="https://github.com/RealAlexandreAI/json-repair">
<img src="images/logo.png" alt="Logo" width="80" height="80">
</a>
<h3 align="center">json-repair</h3>
<p align="center">
JSON Repair: Solution for JSON Anomalies from LLMs.
<br />
<a href="https://goplay.tools/snippet/zyLfsLcsTwg">Online Playground</a>
·
<a href="https://github.com/RealAlexandreAI/json-repair/issues/new?labels=bug&template=bug-report---.md">Report Bug</a>
·
<a href="https://github.com/RealAlexandreAI/json-repair/issues/new?labels=enhancement&template=feature-request---.md">Request Feature</a>
</p>
</div>
<!-- ABOUT THE PROJECT -->
## 🔧 Repair JSON! Solution for JSON Anomalies from LLMs
Welcome to the json-repair, your go-to solution for fixing those pesky JSON anomalies that can sidetrack your Large
Language Model (LLM) processes. Our toolkit is designed to be the Swiss Army knife for all your JSON repair needs.
### 🎯 Why Choose JSON Repair?
- 🏎️ GO Compatibility: Our library ensures a seamless experience for Go developers with its excellent compatibility.
- 🔗 Zero Dependencies: We've crafted a tool with zero external dependencies, keeping it lean and mean.
- 📚 Rich Test Cases: Benefit from a comprehensive suite of test cases that ensure reliability and accuracy.
- 🤖 Auto-Detection & Repair: Intelligently identifies and corrects a wide range of JSON errors, from syntax to
structural issues.
- 📐 Terminal CLI Support: The feature can also be used in the command-line and can be chained with command pipes.
- ⚙️ No Anxiety About Error: json-repair always gives the string result.
- 🌐 Open Source: Join a vibrant community of developers contributing to the ongoing evolution of the toolkit.
### 🔍 Supported Broken LLM JSON Output
- Single quote `"`
- Line feed `\n`
- Improperly formatted JSON string `{"key": TRUE, "key2": FALSE, "key3": Null `
- String with mixed quotes `{'key': 'string', 'key2': false, \"key3\": null, \"key4\": unquoted}`
- Unclosed array `[1, 2, 3, 4`
- Unclosed array object `{"employees":["John", "Anna",`
- Standalone left bracket `[`
- Standalone right bracket `]`
- Array with extra line breaks `[[1\n\n]`
- Incorrect key-value pair `{foo: [}`
- Correct JSON string `{"text": "The quick brown fox won\'t jump"}`
- Incorrect key-value pair `{"value_1": "value_2": "data"}`
- JSON string with comment `{"value_1": true, COMMENT "value_2": "data"}`
- JSON string with leading spaces `- { "test_key": ["test_value", "test_value2"] }`
- String containing a link `{ "content": "[LINK]("https://google.com")" }`
- Unclosed link string `{ "content": "[LINK](" }`
- Unclosed link and extra key string `{ "content": "[LINK](", "key": true }`
- Incorrect key-value pair `{"key":"",}`
- etc.
<p align="right">(<a href="#readme-top">back to top</a>)</p>
<!-- GETTING STAExcerpt of 8,196 characters
Read on GitHubWould you bet a product on this? Bounded 0–100 and slow moving.
matched fp:4df0af350f884836, topic:workflow