# symfony/translation-contracts

Generic abstractions related to translation

Repository: https://github.com/symfony/translation-contracts
Canonical: https://ross.abutalabs.com/products/translation-contracts
Homepage: https://symfony.com
Language: PHP
License: MIT
License Family: permissive
Topics: php, symfony, abstractions, contracts, decoupling, interfaces, interoperability, standards, symfony-contracts
Last push: 2026-06-27T21:46:36+00:00

## Health v2 (maintenance only)
Score: 87/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 89, release rhythm 78, longevity 100
- inputs: {"age_days": 2655, "days_push": 67, "days_rel": 67, "gap_med": 52, "n_releases_24m": 2}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 2584, forks 3 (observed 2026-08-28T04:07:02.578839+00:00)

## What it is
A set of PHP interfaces and abstractions for translation, extracted from the Symfony framework's translation component. It lets libraries depend on stable, battle-tested semantics for translation without coupling to a specific Symfony implementation.

## Use cases
- decouple my PHP library from the Symfony translator implementation
- type-hint against a standard translation interface in PHP
- make my package interoperable with Symfony translation
- add i18n abstractions to a framework-agnostic PHP app
- swap translation implementations without changing consuming code
- define a contract for translatable messages in PHP

## When to choose
- you are building a PHP library or bundle that needs translation support without a hard dependency on symfony/translation
- you want interoperability with the Symfony ecosystem's translation semantics
- you need stable interfaces to program against while allowing different translator backends

## When to avoid
- you need an actual working translator with loaders, catalogs, and message formatting - use symfony/translation instead
- your project does not use PHP
- you only need translation inside a full Symfony application, where the component is already included

## Facets
- artifact type: library
- maturity: stable
- function: internationalization, plugin-system
- domain: web-development, developer-tools
- platform: php
- tags: symfony, contracts, interfaces, abstractions, decoupling, interoperability, translation, localization, composer

## Member repositories
- symfony/translation-contracts (main) score 87

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:07:02.578839+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-30T02:22:29.623546+00:00, confidence not recorded.
  - readme: https://github.com/symfony/translation-contracts (fetched 2026-08-28T04:07:02.578839+00:00, sha 2fb6a2b03277)
  - homepage: https://symfony.com (fetched 2026-08-29T10:05:00.554672+00:00, sha 68595089eb73)
  - site_page: https://symfony.com/doc (fetched 2026-08-29T10:05:00.557296+00:00, sha 44889134f4fb)
  - site_page: https://symfony.com/doc/current/contributing/community/releases.html (fetched 2026-08-29T10:05:00.559133+00:00, sha e46dc2ffbd61)
  - site_page: https://symfony.com/releases (fetched 2026-08-29T10:05:00.560977+00:00, sha 2fd410222cfe)
  - site_page: https://symfony.com/blog/category/releases (fetched 2026-08-29T10:05:00.562992+00:00, sha b626b5bb1423)
- Data as of 2026-08-30T08:39:29.467469+00:00.