By language · PHP
Abandoned PHP packages looking for a new maintainer
Packagist (Composer's registry) has a formal abandoned flag with a use X instead replacement field. Composer surfaces the warning on every install. Adoption signals use the same GitHub adopt-me topic as every other language.
Published July 13, 2026 · ~3 min read
The short version
- Packagist's
abandonedflag is the ecosystem-level signal — Composer shows a warning on every install. - The
replacement packagefield is optional — leave it empty if there's no successor. - The standard signal vocabulary is the GitHub
adopt-metopic +looking-for-maintainerbadge + a pinned issue. - Bus factor 1 + 12 months no release + unanswered issues = adoption candidate.
How to find abandoned PHP packages
The BreakPoint feed filtered to PHP, the GitHub adopt-me topic filtered to PHP, and Packagist packages with the abandoned flag. Composer surfaces the warning in every composer install output, so any project that depends on an abandoned package will have a visible warning in their CI logs. A simple way to find candidates: composer outdated on your own projects and look for the abandoned marker.
If you maintain: Packagist abandoned + GitHub signals
In your packagist.org package settings, mark the package as abandoned and provide a replacement package if there is one. The package stays on Packagist — Composer just warns. Also push a final release with a DEPRECATED note, add the GitHub adopt-me topic, the looking-for-maintainer badge, and a pinned issue. Drop the project on BreakPoint. The PHP community is on r/PHP and the PHP Discord — a "this is a good PHP package looking for a new maintainer" post will get traction.