Some people want to use Composer to install/manage their Drupal site. We have already many core issues around this topic. A important part in the composer ecosystems are package repositories. These repositories store information about all available packages.

Drupal does not use Composer to specify dependencies between Drupal modules and themes nor has every module an additional composer.json in its repo. Therefore we build a composer repository for the Drupal community which converts info files to a composer.json. This repository is hosted on and contains all modules for Drupal 7 and 8. (The source code is on github

We use different sources to get updates from modules (e.g. releases.tsv) but thats not an ideal solution because its not fast enough and the package definition is already a little bit out of date.

Technically speaking: I'd like to use a post-receive hook on infrastructure to get information about any change in any module.

Is this a feasible solution? Maybe one day, if Drupal uses Composer for Module dependencies we could move the whole project to d.o infrastructure.

Thanks to everyone who contributed to drupal-packagist so far especially winmillwill, derhasi, davidbarratt, kasperg, tstoeckler and greg.1.anderson.

Proposed resolution

Remaining tasks

User interface changes

API changes


webflo’s picture

Mile23’s picture

webflo’s picture

Issue summary: View changes
timmillwood’s picture

Status: Active » Closed (won't fix)
derhasi’s picture

I guess this is a "won't fix" because when we support directly, we won't need that change. Is it so?

timmillwood’s picture

Right, closed in favour of using efforts towards #2547617: Notify Packagist about repository update.

Mixologic’s picture

Status: Closed (won't fix) » Closed (duplicate)

Marking this as a duplicate so that future people that land on this issue see its actually being worked on, but somewhere else.