mcamara/laravel-localization

Easy localization for Laravel

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 1 hour ago
Added to GitGenius on September 19th, 2026
Created on August 25th, 2013
Open Issues & Pull Requests: 11 (+0)
GitHub issues: Enabled
Number of forks: 510
Total Stargazers: 3,558 (+0)
Total Subscribers: 87 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 43.0 days
Mean response time: 320.4 days
90th percentile: 967.1 days
Tracked items: 94

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 6
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 1,571 days
Stale 30+ days: 6
Stale 90+ days: 6

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (15)
  • feature request (9)
  • question (2)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Laravel Localization is a Laravel package that provides easy internationalization and localization for multi-language applications.

The package solves the problem of managing multiple language versions of a Laravel application by automatically generating localized routes and detecting user language preferences. It works by intercepting requests, detecting the desired language from the URL, browser headers, or stored session/cookie data, and dynamically generating routes for each supported locale. The package allows developers to define routes once and have them automatically available in all configured languages, with support for translatable route segments.

The tool suits Laravel applications that need multi-language support without manually creating separate route definitions for each language. It is particularly useful for projects that want to hide the default locale from URLs, automatically detect user language from browser preferences, or provide language selection helpers. The README explicitly recommends that new projects or applications planning to migrate should use the modern successor package instead, which supports route caching natively through statically registered routes rather than dynamic generation per request. Existing users who need to stay on the current architecture can continue using this package.

The project remains actively maintained for compatibility updates with new Laravel and PHP versions, security fixes, and small bug fixes. The package supports caching and testing workflows, though route caching requires workarounds in the current architecture. The maintainers continue to provide support for users who depend on the existing dynamic routing approach.