The League of Extraordinary Packages
@thephpleague • A group of developers who have banded together to build solid, well tested PHP packages using modern coding standards.. Use this route to separate flagship concentration from portfolio breadth before you treat a publisher as broadly strong.
Portfolio concentration
76%
Top three share
Shows whether the organization is driven by one breakout repo or several visible projects.
Breadth
30 repos
Visible snapshot
7 repositories updated in the last 90 days.
Leading language
PHP
Portfolio mix
PHP (30)
Average size
109
Stars per repository
Useful for distinguishing one flagship-heavy publisher from a repeatable portfolio.
Updated: 2026-10-03(7d ago)GitHub API fallback30 repositories
76%
of the visible star count comes from this organization's top three repositories.
109
stars per repository in this same snapshot.
PHP
is the most common language here, with 7 repositories updated in the last 90 days.
Why this rank
This organization stands out because its public portfolio is relatively balanced across 30 repositories.
Balanced portfolio across 30 reposTop 3 share 76%
Organization pages work best when you separate portfolio breadth from flagship concentration. In The League of Extraordinary Packages's case, the visible top three repositories account for about 76% of total stars in this snapshot, which helps explain whether the organization is known for one breakout project or for a broader repeatable portfolio.
The dominant language mix here is PHP (30). That makes this page useful not just for popularity checks, but also for seeing what technical shape an organization's public ecosystem actually has.
Top Repositories
Next step after the organization read
Open a flagship repository, compare a couple of portfolio leaders, or return to the organization map when you want a broader concentration read.
Learn and methodology
Keep trust-building context reachable, but behind the first data read instead of ahead of it.
How to read this organization snapshot
Total stars are useful as a discovery signal, but they do not tell you whether a team maintains every repository equally. Pair this page with release cadence, maintainer activity, and the flagship concentration shown above before making adoption decisions.
For broader background on GitStar's ranking logic and editorial guidance, see Methodology & Editorial Standards.