Awesome PHP is a link list whose only snapshot is the master branch

One README file, no package, nothing to install

The entire project is a repository with seven top-level entries: a README, three governance files covering contributing, collaboration and code of conduct, a licence, an editor config, and a .github directory. There is no source directory, no build step, no manifest and no executable. You read the page or you clone the repository and read the page.

That has a direct consequence for how you should judge an entry. The list cannot tell you a library's version, its PHP requirement, its release date, or whether its maintainer answered an issue last month, because none of that data is captured anywhere in it. Every link is a bare name, a URL, and a sentence of description, often a single clause.

So the value is discovery and the limit is verification. A section header tells you a category exists and roughly how crowded it is, which is genuinely useful when you have no idea where to start. Deciding whether a given entry belongs in your project takes a second step the list cannot take for you, and that second step is the whole of the real work.

The Composer entries are the biggest section, and two of them are paid

The list opens with Composer Repositories, and the entries there are not interchangeable. Packagist is the main package repository. Private Packagist is described as a Composer package archive as a service, and Repman is a private package repository manager and Packagist proxy. Both of those are commercial products sitting in the same bullet list as the free ones, with no marker distinguishing them.

The dependency management section is broader. Composer itself is the package and dependency manager, Composer Installers is a multi-framework installer library, Phive is a PHAR manager, and two entries are extension installers: Pickle from FriendsOfPHP and Pie, which is described as the official PHP installer for extensions.

That last entry is the one with a shelf life. Once an official installer exists, the community alternatives are solving a problem the language now handles, and a reader picking between them should notice which one carries an official designation. The section also carries quality plugins that most people never install but should know exist, including Composer Prefer Lowest Validator, Composer Require Checker and Composer Unused, all aimed at keeping a dependency tree honest.

Phalcon and Spiral are the two framework entries that are not pure PHP

Most entries in the Frameworks section are ordinary PHP. CakePHP, CodeIgniter, Laravel, Nette, Symfony, Tempest and Yii2 all fall in that group, and Laminas is noted as a framework of individual components that was previously Zend Framework, which tells you a rename happened and that old tutorials may use the old name.

Two break the pattern. Phalcon is implemented as a C extension, which is why its performance characteristics and its installation requirements differ from everything else in the section. Spiral is described as a high-performance PHP/Go framework, so part of it lives outside the language. Ecotone sits apart for a different reason: it is a service bus built on DDD, CQRS and event sourcing principles rather than a request-response web framework.

The practical consequence is that the Frameworks section is not a like-for-like comparison list. Three of the eleven entries are architecturally different from the rest, and choosing between Phalcon and Symfony is choosing between a compiled extension and interpreted PHP, not between two frameworks. Read the one-line descriptions as the selection criteria, because they carry the distinctions that matter.

An LLMs section sits between Configuration and Third Party APIs

The table of contents runs to around seventy categories, and the list has kept absorbing new ones as PHP has grown. There is a Serverless section, a Caching and Locking section, a Notifications section, an Imagery section, and near the end an LLMs section placed between Configuration and Third Party APIs.

That placement is the interesting part. The surrounding categories are all things a PHP application integrates directly: configuration files, external HTTP services, caching backends. An LLM provider belongs to the same family, so the section reads as an attempt to treat model access the way the list already treats a payment gateway or a mail service.

What it cannot do is tell you which of those entries overlap, which maintain a compatible version, or which are thin wrappers around the same HTTP endpoint. A section header here is a signpost, not a comparison. Anyone evaluating model access through this list still has to establish interface stability, rate limits and pricing per provider, none of which appear in a bullet with a URL next to it.

The second half is not libraries at all

Past the library sections the document changes character twice. The Software half covers PHP Installation, Development Environment, Virtual Machines, Text Editors and IDEs, Web Applications and Infrastructure. The Resources half covers PHP Websites, Books, Videos, Conferences, Podcasts, Newsletters, Reading and PHP Internals Reading.

That structure has a real effect on how the list ages. A library link that points at a maintained project stays good indefinitely, because the project keeps existing. A conference or a newsletter link is a point-in-time reference, and it is the entries most likely to rot without anyone noticing. The two halves have opposite half-lives, and the page presents them with equal confidence.

The PHP Internals Reading category is the exception worth singling out, because it points at how the language itself is documented rather than at any library. For someone who wants to understand why a function behaves the way it does, that section is the one part of the list where the underlying material changes on the engine's schedule rather than a maintainer's.

WTFPL covers the list, and says nothing about any entry in it

The repository is licensed WTFPL, and there is a licence file at the root. That is a deliberately permissive choice and it fits a document of links, since the page is meant to be copied and republished.

The important point is the boundary. A licence attached to an index covers the index. It does not extend to the hundreds of projects named inside it, and those projects carry their own terms, some open source, some source-available, some commercial subscriptions with a paid tier. Composer itself, Private Packagist, Repman and a paid source of hosting or monitoring all appear in these sections. Nothing in the list marks which is which.

So read the licence as covering the page, and read the licence of anything you install. The gap between those two readings is where a team can end up shipping something whose terms nobody checked, because the list gave no signal that checking was needed.

Pull requests to master, and no release is ever cut

The repository is not archived, and the last push was 2026-09-27. There are no GitHub releases and no version tags, so the master branch is the only state of the document that has ever existed. There is no v1, no v2, and no way to pin to a moment you were happy with.

That has a concrete consequence. If a good link is replaced or removed, you have nothing to fall back to, because the old value is not preserved in any published artifact. For a resource that people bookmark and return to, that is worth knowing before you rely on it as a reference you can point colleagues at.

Contribution runs through the contributing and collaborating files at the repository root, and the presence of both, plus a code of conduct, suggests a project with a defined process rather than an open pull request queue. The governance is written down but lives in those files rather than in the page itself, so anyone planning to submit an entry has to go read them first.

Editorial conclusion

Use Awesome PHP the way it is built: as an index for finding a category quickly, then evaluate each entry on its own repository before adopting it. Do not treat the list as a dependency source, a compatibility check, or a security signal, because it carries none of those. Before you take any entry from it, open its own repository and read its last commit and its own licence, since the list itself is WTFPL and that says nothing about the hundreds of projects it points at, several of which are commercial services rather than open source.

Frequently asked questions

Official sources

1. Official README
2. Project repository