Packagist is the main Composer repository. It aggregates public PHP packages installable with Composer. Search by What is Packagist? Packagist is the default Composer package repository. It lets you find packages and lets Composer know where to get the code from. You can use Composer to manage your project or libraries' dependencies - read more about it on the Composer website.
You can find the packagist. Community If you have questions about composer or want to help out, come and join us in the composer channel on irc. You can find more community resources in the Composer documentation. If you would like to financially support the hosting and maintenance of the project, the best way is to check out and use Private Packagist. It can help you install packages fast and reliably, provides you with a private package repository, and the money goes towards Composer and Packagist maintenance!
How to submit packages? Naming your package First of all, you must pick a package name. This is a very important step since it can not change and it should be unique enough to avoid conflicts in the future. The vendor name exists to prevent naming conflicts. In some cases the vendor name and the package name may be identical. For projects with a unique name this is recommended. It also allows adding more related projects under the same vendor later on.
If you are maintaining a library, this would make it really easy to split it up into smaller decoupled parts. Here is a list of typical package names for reference: This can of course be packages, not only a php version. You can use ext-foo to require php extensions e. Note that most extensions don't expose version information, so unless you know for sure it does, it's safer to use "ext-curl": Finally the type field is in this case indicating that this is a library.
If you do plugins for frameworks etc, and if they integrate composer, they may have a custom package type for their plugins that you can use to install the package with their own installer.
In the absence of custom type, you can omit it or use "library". Once you have this file committed in your repository root, you can submit the package to Packagist by entering the public repository URL. Managing package versions New versions of your package are automatically fetched from tags you create in your VCS repository.
The easiest way to manage versioning is to just omit the version field from the composer. The version numbers will then be parsed from the tag and branch names. Z', with an optional suffix for RC, beta, alpha or patch versions. Here are a few examples of valid tag names: The use of Semantic Versioning is strongly encouraged. Update Schedule New packages will be crawled immediately after submission if you have JS enabled.
When a hook is enabled packages are crawled whenever you push, or at least once a month in case the crawl failed. You can also trigger a manual update on your package page if you are logged-in as a maintainer. This reduces the load on our side, and ensures your package is updated almost instantly. Check the how-to below. The search index is updated every five minutes.
It will index or reindex any package that has been crawled since the last time the search indexer ran. How to update packages? GitHub Service Hook Enabling the Packagist service hook ensures that your package will always be updated instantly when you push to GitHub. To do so you can: Go to your GitHub repository Click the "Settings" button Add a "Packagist" service, and configure it with your API token, plus your Packagist username Check the "Active" box and submit the form You can then hit the "Test Service" button to trigger it and check if Packagist removes the warning about the package not being auto-updated.
Bitbucket Webhooks To enable the Bitbucket web hook, go to your BitBucket repository, open the settings and select "Webhooks" in the menu. Add a new hook. You have to enter the Packagist endpoint, containing both your username and API token. Save your changes and you're done.
Manual hook setup If you do not use Bitbucket or GitHub there is a generic endpoint you can call manually from a git post-receive hook or similar. You have to do a POST request to https: