[READ-ONLY] URI manipulation Library
1.1k
Stars
71
Forks
0
Open issues
30
Contributors
AI Analysis
A PHP library for RFC-compliant URI manipulation and parsing, providing simple object-oriented abstractions for working with URIs in compliance with PSR-7 standards. It serves developers who need robust URI handling in PHP applications, particularly those working with web standards and HTTP clients. Not suitable for non-PHP environments or projects requiring minimal dependencies.
Inferred from signals mentioned in the README (tests, CI, type safety) — not a review of the actual code.
AI's overall editorial judgment — not an average of the bars above, can weigh other factors too.
Mature PHP URI library from The League with steady adoption, focused on RFC-compliant manipulation rather than dominance.
League URI is a PHP package for parsing, validating, and manipulating URIs according to RFC 3986/3987 standards. Built for developers who need predictable, standards-compliant URI handling in PHP applications. Adopted by projects requiring strict RFC compliance and IDN support. Maintained as part of The League's ecosystem of specialized libraries, not positioned as a general-purpose replacement for built-in PHP functions but as a more rigorous alternative for complex URI work.
Created in July 2015 as part of The League (thephpleague), a collective of PHP maintainers producing focused, PSR-compliant libraries. URI joined a portfolio that already included Flysystem, Plates, and CommonMark. Evolved through refinement rather than feature explosion, reflecting a philosophy of solving URI problems thoroughly rather than broadly.
Star count (1,130) and fork activity (71) suggest modest, stable adoption. No growth spike detected in recent weeks (0 stars gained last 7 days as of current date 2026-06-27). This reflects the library's positioning: not aiming for viral adoption but serving teams that specifically need RFC-compliant URI handling. Growth likely driven by PSR-7 ecosystem adoption and frameworks requiring proper URI abstraction rather than marketing.
Adoption not verified with specific user counts or high-profile public case studies in available metadata. Packagist download metrics mentioned but not quantified in README. PSR-7 ecosystem integration and presence within The League (which includes widely-adopted projects like Flysystem with 13.5k stars) suggests indirect production usage. Likely used by frameworks and middleware implementing PSR-7 interfaces, but direct evidence absent.
Based on README: appears to provide classes for URI management with PSR-7 compliance. Requires PHP 8.1+. Integrates with League URI Interfaces package. Likely uses object-oriented design with immutable URI objects (standard for PSR-7 implementations). Optional dependencies on intl extension (IDN support), GMP/BCMath (IPv4 conversion), and dom extension (HTML content handling) suggest modular optional features rather than monolithic design.
Not documented in README. League projects generally maintain high test standards, but specific coverage metrics are not provided in available metadata.
Last push 2026-03-15 (approximately 3 months before analysis date). Indicates active maintenance, though push frequency not specified. Repository marked as 'READ-ONLY' sub-split with development directed to thephpleague/uri-src, suggesting organized monorepo-style maintenance. No indicators of abandonment or crisis maintenance.
ADOPT IF: you need RFC 3986/3987 compliant URI handling, work within PSR-7 ecosystems, require IDN support, or manipulate complex URIs in library/framework code where correctness matters more than convenience. AVOID IF: you only need basic URL parsing (built-in parse_url suffices), are building simple scripts where dependency overhead outweighs benefit, or your team lacks familiarity with object-oriented URI abstractions. MONITOR IF: you are evaluating it for new projects and want to confirm ongoing maintenance (currently active as of March 2026) and ensure your team understands the learning curve vs. simpler alternatives.
Independent dimensions
Mainstream potential
3/10
Technical importance
7/10
Adoption evidence
4/10
- Adoption appears limited to PHP teams specifically valuing RFC compliance; may struggle to gain traction in codebases defaulting to built-in functions or simpler approaches.
- Dependency on optional extensions (intl, GMP/BCMath, dom) could complicate deployment in environments with restricted extension availability.
- README does not quantify download metrics or provide adoption case studies; real-world usage scale remains unclear despite likely production use.
- Niche positioning (RFC correctness over convenience) may limit appeal to teams where URI handling is incidental rather than core concern.
- Sub-split architecture (development at uri-src) could create friction for contributors unfamiliar with monorepo patterns.
League URI will likely remain a stable, actively maintained specialist library serving teams that explicitly value RFC compliance and PSR-7 integration. Unlikely to become dominant in general PHP URL handling (parse_url and string manipulation will remain default), but appears positioned for sustained use in middleware, framework internals, and HTTP client libraries where correctness is non-negotiable. Growth will remain incremental rather than exponential.
Newsletter
Get analyses like this every Monday
Free weekly digest of the most interesting open-source discoveries.
Languages
Information
- Website
- https://uri.thephpleague.com
- Language
- PHP
- License
- MIT
- Last updated
- 4mo ago
- Created
- 134mo ago
- Analyzed with
- anthropic/claude-haiku-4-5
Stars over time
Contributors over time
Top 100 contributors only — repos with more will plateau at 100.
Open issues
No open issues — clean slate.
Open pull requests
No open pull requests.
Top contributors
Similar repos
jeremykendall/php-domain-parser
PHP Domain Parser is a specialized library for accurately parsing domain names...
thephpleague/geotools
Geotools is a PHP library for geolocation and geometry operations, built on...
thephpleague/plates
Plates is a native PHP template system that uses vanilla PHP syntax rather than...
| Repository | Stars | Week Δ | Language | Score | Updated |
|---|---|---|---|---|---|
|
thephpleague/uri
this
|
1.1k | +2 | PHP | 8/10 | 4mo ago |
|
thephpleague/csv
|
3.5k | — | PHP | 8/10 | 1w ago |
|
jeremykendall/php-domain-parser
|
1.2k | — | PHP | 8/10 | 5mo ago |
|
thephpleague/geotools
|
1.4k | — | PHP | 7/10 | 4mo ago |
|
thephpleague/plates
|
1.5k | — | PHP | 7/10 | 6mo ago |
|
thephpleague/flysystem
|
13.6k | — | PHP | 8/10 | 3w ago |
League URI provides stricter RFC compliance, immutable objects, and structured manipulation vs. built-in functions that return arrays and lack RFC enforcement; trade-off is dependency and complexity.
League URI is standalone and more granular; Guzzle bundles HTTP client with URI handling; League approach better for projects needing URI logic decoupled from HTTP transport.
League URI implements PSR-7 standard alongside own API; competes/cooperates with other PSR-7 implementations depending on project requirements.
Symfony's URI handling is embedded in HttpFoundation; League provides standalone option for non-Symfony projects valuing spec compliance.
League offers object model and immutability; string-based approach is simpler for trivial cases but harder to maintain at scale.
