Sign in

Tags / LLM tools /

Structured output

A library that makes LLM output follow a schema such as JSON, through parsing, validation, or constrained decoding.

Repositories

8

Net stars gained, last 7 days

+623

Top-level Tag

LLM tools

Net stars gained each day, last 90 days

2026-09-18: +425 net stars. Most from vercel-labs/json-render, +392.2026-09-20: +726 net stars. Most from vercel-labs/json-render, +674.2026-09-21: +486 net stars. Most from vercel-labs/json-render, +409.2026-09-23: +360 net stars. Most from nokia-applied-research/AnyJev, +240.2026-09-25: +381 net stars. Most from nokia-applied-research/AnyJev, +215.

Peak days

  1. 1

    Sep 18, 2026 +425 net stars (median day +69)

  2. 2

    Sep 20, 2026 +726 net stars (median day +69)

  3. 3

    Sep 21, 2026 +486 net stars (median day +69)

  4. 4

    Sep 23, 2026 +360 net stars (median day +69)

  5. 5

    Sep 25, 2026 +381 net stars (median day +69)

A peak day has at least 2 times the net stars of the median day of this chart, and at least 100 more. For each peak day, the list shows the repositories that gained the most net stars that day. It also shows their GitHub releases of that day or the day before (UTC), and their creation date when it was 14 days or less before. These events occur near the same day. They do not show why the stars came.

Largest

Most stars in total now.

  1. readme: Enforces a consistent output schema based on your few-shot examples, leveraging controlled generation in supported models like Gemini to guarantee robust, structured results.

  2. readme: A JSON schema is actually a context free grammar, and hence it can be used to constrain an LLM using Guidance.

  3. readme: Give the agent an output type and tools, and every run comes back validated and typed:

  4. readme: AI generates interfaces from natural language prompts, constrained to components you define.

  5. readme: Outlines guarantees structured outputs during generation — directly from any LLM.

  6. readme: Instructor provides automatic validation, retries, streaming, and nested object support.

  7. description: Turn any LLM into a Jev-style decision model: typed decisions, real probabilities, no training.

  8. readme: Replies are written in each model's own tool-call format under a grammar applied on the GPU

Newest Admissions

Entered the index by the rising rule, newest first.

  1. readme: Replies are written in each model's own tool-call format under a grammar applied on the GPU

  2. description: Turn any LLM into a Jev-style decision model: typed decisions, real probabilities, no training.

All 8 in the Repository Index

How a repository gets this Tag

An agent reads the description, the GitHub topics, and the start of the README of each repository. It chooses Tags only from the Tag list in the AwesomeRepos source code. For each Tag, it quotes the text. A code check keeps the Tag only when the quote is in that text. The quote under each repository is that evidence. A Tag does not rank repositories. It does not say that one repository can replace another. To report a wrong Tag, use "Report a problem with this page" on the page of the repository. All numbers on this page count only visible repositories.