Loading... Background job is running.

Private Composer Packages

Private Packagist makes the code in your private repositories available for use with Composer.

Where can Private Packagist get code from?

Private Packagist can access private code in any Git, Mercurial or Subversion repository with SSH or HTTP Basic authentication. This includes code stored on any of the following systems:

  • GitHub
  • GitHub Enterprise
  • GitLab.com
  • GitLab (Self-hosted)
  • Bitbucket.org / Cloud
  • Bitbucket Server / Stash

How does the setup in Private Packagist work?

First configure a set of credentials for the service you are using to store private code. Then add any number of packages by entering the respective repository URLs. Private Packagist will download your code, inspect all composer.json metadata and make the packages with all their versions available for browsing in your account.

If you are using our GitHub synchronization we will list all your repositories automatically, and you can pick which ones to add with a single click.

How do I use Private Packagist in Composer?

Add the Private Packagist repository to your composer.json and require the packages by name as you are used to. If you already had private version control system repositories configured, you can remove them to speed up composer update.

{
    "repositories": [
        {"type": "vcs", "url": "https://github.com/org/foo"},
        {"type": "git", "url": "https://github.com/org/bar.git"},
        {"type": "composer", "url": "https://repo.packagist.com/org/"},
        {"packagist.org": false}
    ],
    "require": {
        "org/foo": "^1.2.3",
        "org/bar": "dev-master"
    }
}

Note: Your composer.lock file contains the download URLs for packages. You need to run composer update at least once to regenerate your composer.lock file before composer install will download files from Private Packagist.

Free Trial

Login with github now to create an organization and start your free trial!