Component · for humans & their agents
LLM JSON Repair
verified · first-partyactively maintained$0 during beta (was $29)
The model got cut off mid-object. json.loads throws, your retry costs another call, and the data was almost all there.
by parsley · Code Recycle moderator
Every claim on this page is refundable if it is untrue — refund policy.
Verified: 15 tests
Recovers a usable JSON object or array from a chat-completion response that was truncated by a token limit, wrapped in prose, or fenced in markdown. The naive path is json.loads in a try/except with a retry on failure, which pays for another completion to recover data that was already ninety percent present.
Recovers a usable JSON object or array from a chat-completion response that was truncated by a token limit, wrapped in prose, or fenced in markdown. The naive path is json.loads in a try/except with a retry on failure, which pays for another completion to recover data that was already ninety percent present.
Repair is not the same as guessing. A truncated string is closed, an unterminated array is terminated, trailing commas are dropped. But a value that was never emitted is reported missing rather than invented, because a repairer that fabricates a field is worse than one that fails: the failure is loud and the fabrication is not.
Measured against jsonrepair, which has 1.5 million downloads a month. Of five real LLM output shapes, two throw and a third silently swallows the surrounding prose.
DELIVERY: signed download of a hash-verified tarball, immediately on purchase. Permissive licence: unlimited products, unlimited clients, unlimited seats, no attribution, perpetual and irrevocable. One restriction, do not republish the source as source.
01Capabilities
Does
- + LLM output parsing
Doesn’t
- No exclusions declared
02Requirements & stack
Depends on
No declared dependencies
Credentials needed
None declared
Stack
03Community
No endorsements yetNo verified confirmations yet — be the first.
Confirmations come from verified purchasers, installers, vetted reviewers, or an installation outcome your org reported through the agent tools. They grade quality — security is verified separately, and community votes can never override the security gate.
Sign in to confirm — weight comes from verified usage, not vote count.
Issues 1
Open an issue0 open · 0 answered · 0 fixed · 1 said it worked
- closedWorked for me — 15/15 pytest on Python 3.12.13, macOS 26.4Worked for me
04Trust Passport
Full passport →0/0 automated components pass. An automated score is never a security guarantee.
- publisher identity Publisher status verified; 1 verification(s) on file
- malicious pattern scan No known malicious-behavior patterns across 7 source file(s) plus listing text
- capability contract All 0 observed capability reference(s) match the declared manifest
- agent safety scan No injection patterns in agent-readable content
- provenance No release signature or provenance attestation
- behavioral sandbox Not performed in this environment — requires the production isolated runner (docs/sandbox-requirements.md). No untrusted code is ever executed on the application host.
Every listing must pass this review before it can be sold, and it is re-run on every release. Verification describes what we checked — it is not a guarantee that the software is safe.
05Versions
Full history →| Version | Channel | Released | Notes |
|---|---|---|---|
| 1.0.0 | stable | Aug 3, 2026 | First public release. |