# opral/inlang

Open format TMS (translation management system)

Repository: https://github.com/opral/inlang
Canonical: https://ross.abutalabs.com/products/inlang
Homepage: https://inlang.com
Language: TypeScript
License Family: other
Topics: i18n, localization, localisation, vscode, globalization
Last push: 2026-08-25T17:50:48+00:00

## Health v2 (maintenance only)
Score: 77/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 99, release rhythm 35, longevity 100
- inputs: {"age_days": 1849, "days_push": 8, "days_rel": null, "gap_med": null, "n_releases_24m": 0}
- flags: no_releases, no_license
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1987, forks 178 (observed 2026-08-28T04:06:02.938197+00:00)

## What it is
inlang is an open-format translation management system (TMS) that stores localization data in a vendor-neutral .inlang project file or directory inside your repository. It ships an SDK (@inlang/sdk), plugins for formats like JSON, ICU, i18next, and XLIFF, editor tools, and CI integrations so developers, translators, and AI agents share one localization source of truth.

## Use cases
- manage app translations in git as code
- avoid vendor lock-in from traditional TMS platforms
- run CI checks for missing translations and placeholder issues
- let translators edit strings via a friendly editor while devs use the SDK
- import and export i18next, ICU MessageFormat, JSON, and XLIFF files
- give AI agents programmatic access to localization data

## When to choose
- your team wants translations versioned in the repo alongside code
- you need an open, vendor-neutral localization format with SDK and plugin access
- you want CI automation and editor tooling around i18n files
- engineering, translators, and automation must edit the same source of truth

## When to avoid
- you need a fully managed enterprise TMS with vendor management, translation memory, and procurement features
- you only need a simple i18n runtime library without translation management
- you require a no-code hosted localization dashboard as the primary workflow

## Facets
- artifact type: framework
- maturity: active
- function: internationalization, sdk, plugin-system, developer-tools
- domain: web-development, developer-tools
- platform: cross-platform, editor-plugin, cli
- tags: tms, translation-management, i18n, open-format, lix, vscode-extension, ci-checks, localization, automation, nodejs

## Member repositories
- opral/inlang (main) score 77

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:06:02.938197+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T03:03:01.080618+00:00, confidence not recorded.
  - readme: https://github.com/opral/inlang (fetched 2026-08-28T04:06:02.938197+00:00, sha d9ecb0904032)
  - homepage: https://inlang.com (fetched 2026-08-29T10:43:11.742470+00:00, sha 3b7644c045be)
  - site_page: https://inlang.com/docs (fetched 2026-08-29T10:43:11.752491+00:00, sha 6eb9c9c14eff)
  - site_page: https://inlang.com/documentation (fetched 2026-08-29T10:43:11.755194+00:00, sha 6eb9c9c14eff)
- Data as of 2026-08-30T08:39:29.467469+00:00.