google/langextract

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.