# WP Composer is now WP Packages

When we launched WP Composer, we wanted to give the WordPress community an independent, open source Composer repository. We got the technical part right, but we got the name wrong.

**[WP Packages](https://wp-packages.org/)** is the new name, and [wp-packages.org](https://wp-packages.org/) is the new URL.

## Why the rename

Shortly after launch, Nils Adermann, co-creator of Composer, reached out to us. His feedback was straightforward:

> "We just generally try to keep Composer referring to CLI/client side things and Packagist for the server/repository. Otherwise people just end up getting even more confused by these tools. Eg right now just based on the name I would expect WP Composer to be some Composer fork or plugin to maybe work with WPackagist"

He's right. Our project is a Composer *repository* — it's not a CLI tool, a Composer plugin, or a fork of Composer itself. The name was causing exactly the kind of confusion the Composer team has been working to prevent. On top of that, "Composer" is a registered trademark, as is "Packagist", so we should have done better homework before choosing the name in the first place. We're happy to correct course.

## What's changed

- **Name:** WP Composer → **WP Packages**
- **Domain:** `wp-composer.com` → **`<a href="https://wp-packages.org/">wp-packages.org</a>`**
- **Repository URL:** `repo.wp-composer.com` → **`repo.wp-packages.org`**
- **GitHub:** `roots/wp-composer` → **`<a href="https://github.com/roots/wp-packages">roots/wp-packages</a>`**

Package naming (`wp-plugin/*`, `wp-theme/*`) stays the same. Performance, features, and everything else about the project remain unchanged.

## Do I need to do anything?

If you're already using WP Composer: your existing packages will continue to work, but you will see a warning to migrate.

The WP Composer repo is no longer fetching new updates from WP.org, so when you get a chance, updating your repository config is a quick one-liner:

```
composer config --unset repositories.wp-composer && composer config repositories.wp-packages --json '{"type":"composer","url":"https://repo.wp-packages.org"}'
```

Or update your `composer.json` directly:

```
{
  "repositories": [
    {
      "name": "wp-packages",
      "type": "composer",
      "url": "https://repo.wp-packages.org"
    }
  ]
}

```

**If you're using Bedrock or Radicle:** update to the latest release, which has the new repository URL out of the box.

## Same project, better name

WP Packages is still fully open source, still community-funded through [GitHub Sponsors](https://github.com/sponsors/roots), and still the fastest way to manage WordPress plugins and themes with Composer. We just have a name that actually describes what it is now.

[GitHub](https://github.com/roots/wp-packages) · [Website](https://wp-packages.org)