PHPackages                             metalinspired/multi-composer - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Utility & Helpers](/categories/utility)
4. /
5. metalinspired/multi-composer

ActiveComposer-plugin[Utility & Helpers](/categories/utility)

metalinspired/multi-composer
============================

Composer plugin that helps with dependencies for projects that have multiple composer instances

1.0.1(2y ago)019MITPHPPHP ^7.2.5 || ^8.0

Since Dec 6Pushed 2y ago1 watchersCompare

[ Source](https://github.com/metalinspired/multi-composer)[ Packagist](https://packagist.org/packages/metalinspired/multi-composer)[ RSS](/packages/metalinspired-multi-composer/feed)WikiDiscussions master Synced 1mo ago

READMEChangelog (2)Dependencies (4)Versions (3)Used By (0)

Composer plugin that helps with dependencies for projects that have multiple composer instances
===============================================================================================

[](#composer-plugin-that-helps-with-dependencies-for-projects-that-have-multiple-composer-instances)

If you're stuck in situation where a project has to have two (or more) composer instances, and they require (and install) same packages this plugin will help you by reusing installed packages from one of those instances.

It achieves this by reading the `composer.lock` and generating (and injecting) a list of provided and conflicting packages.

Installation
------------

[](#installation)

1. Add your source composer instance as repository to `composer.json`

    ```
    "repositories": [
       {
         "type": "path",
         "url": "../where_other_composer_is_installed",
         "options": {
           "symlink": true
         }
       }
    ]

    ```
2. Install this plugin (confirm with "y" that you trust and want to enable the plugin)

    ```
    composer require metalinspired/multi-composer

    ```
3. Configure the plugin

    ```
    "extra": {
      "multi-composer": [
        {
          "package": "your-vendor-name/your-project-name:dev-main",
          "autoload_psr-4": false,
          "skip_dev": false
        }
      ]
    }

    ```
4. Require your source composer instance

    ```
    composer require your-vendor-name/your-project-name:dev-main

    ```

Configuration options
---------------------

[](#configuration-options)

`package`: String with name and version of your source composer instance. This must be provided in the same form as when requiring your source composer instance (project-name:version)

`autoload_psr-4`: Optional boolean indicating whether to include PSR-4 namespace(s) defined in your source composer instance.

*Note:* This only works when you install (request) your source composer instance. Changing the value of this and updating will have no effect. You will have to remove and require again (reinstall does not work) your source composer instance.

`skip_dev`: Optional boolean indicating should *dev* dependencies be skipped. This is useful if your source composer instance has same *dev* requirements but does not have them installed.

###  Health Score

23

—

LowBetter than 27% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity6

Limited adoption so far

Community7

Small or concentrated contributor base

Maturity52

Maturing project, gaining track record

 Bus Factor1

Top contributor holds 100% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~259 days

Total

2

Last Release

991d ago

### Community

Maintainers

![](https://www.gravatar.com/avatar/6d9bfe1b062ffcfed45fc969e1c354add7e44a6dbf3216dd587fc660f53ce155?d=identicon)[metalinspired](/maintainers/metalinspired)

---

Top Contributors

[![metalinspired](https://avatars.githubusercontent.com/u/18539473?v=4)](https://github.com/metalinspired "metalinspired (3 commits)")

###  Code Quality

Static AnalysisPsalm

Code StylePHP\_CodeSniffer

Type Coverage Yes

### Embed Badge

![Health badge](/badges/metalinspired-multi-composer/health.svg)

```
[![Health](https://phpackages.com/badges/metalinspired-multi-composer/health.svg)](https://phpackages.com/packages/metalinspired-multi-composer)
```

###  Alternatives

[vaimo/composer-patches

Applies a patch from a local or remote file to any package that is part of a given composer project. Patches can be defined both on project and on package level. Optional support for patch versioning, sequencing, custom patch applier configuration and patch command for testing/troubleshooting added patches.

2994.3M15](/packages/vaimo-composer-patches)[mglaman/composer-drupal-lenient

1317.4M15](/packages/mglaman-composer-drupal-lenient)[drupal/core-composer-scaffold

A flexible Composer project scaffold builder.

5341.9M441](/packages/drupal-core-composer-scaffold)[drupal/core-project-message

Adds a message after Composer installation.

2122.6M172](/packages/drupal-core-project-message)[olvlvl/composer-attribute-collector

A convenient and near zero-cost way to retrieve targets of PHP 8 attributes

184108.8k8](/packages/olvlvl-composer-attribute-collector)[lullabot/drainpipe

An automated build tool to allow projects to have a set standardized operations scripts.

41716.4k2](/packages/lullabot-drainpipe)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)