Discofork
Repository brief

google/langextract

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis
cached 2026-03-31T09:50:49.347Z
1mo ago

google/langextract

LangExtract is a Python library for LLM-based structured extraction from unstructured text, with explicit source grounding, interactive HTML visualization, and support for cloud and local models. It looks active and mature: Apache-2.0, Python 3.10+, version 1.2.0, 35k+ stars, 2.3k+ forks, and recent commits in March 2026.

GitHub
Loading tags...
Stars35,033
Forks2,368
Default branchmain
Last pushed2026-03-22T22:11:16Z
Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs
Selected

Prefer upstream unless you need this exact older snapshot. The fork adds no visible value over upstream and is missing several recent fixes and improvements.

Choose this fork only if you want a clean mirror of LangExtract and are comfortable being a few commits behind upstream. If you need the latest provider, chunking, or extraction fixes, upstream is the better default.

Choose this fork if provider extensibility is the priority. Choose upstream if you want the latest core extraction fixes and the lowest-maintenance path.

Prefer this fork if your main goal is publishing and maintaining LangExtract releases. Prefer upstream if you want the newest extraction behavior, provider fixes, and long-document improvements.

Prefer this fork if your main pain point is Chinese text grounding and visualization. Prefer upstream if you need the newest provider and extraction fixes or broad, general-purpose maintenance.

Prefer upstream unless you specifically need this exact older snapshot; this fork adds no evident features and is behind on meaningful fixes and one newer extraction capability.

Prefer this fork if provider extensibility and custom integration are the main goal. Prefer upstream if you want the newest fixes, lower maintenance risk, and the most mature default behavior.

Choose this fork only if you specifically want the contributor-recognition edits; otherwise upstream is the better default because it is newer and functionally richer.

Choose upstream unless you specifically need this exact older snapshot; the fork adds nothing and is already behind several fixes.

Choose this fork only if you want an almost-vanilla LangExtract baseline. For production use, upstream is currently a better default because this fork adds nothing and is behind on fixes and features.