PHPackages                             meeva/composer-monorepo-builder-path-plugin - 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. meeva/composer-monorepo-builder-path-plugin

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

meeva/composer-monorepo-builder-path-plugin
===========================================

composer plugin to install packages grouped via symplify/monorepo-builder as path-symlinks

v2.0.1(4y ago)2196.0k—6.4%2MITPHPPHP >=7

Since Jan 8Pushed 3y ago1 watchersCompare

[ Source](https://github.com/possi/composer-plugin-monorepo-path)[ Packagist](https://packagist.org/packages/meeva/composer-monorepo-builder-path-plugin)[ RSS](/packages/meeva-composer-monorepo-builder-path-plugin/feed)WikiDiscussions master Synced 1mo ago

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

monorepo-builder-path (composer plugin)
=======================================

[](#monorepo-builder-path-composer-plugin)

Composer plugin intended to use in conjunction with [symplify/monorepo-builder](https://packagist.org/packages/symplify/monorepo-builder).

When having a repository of kind:

```
monorepo_dir
 ` bundles
    ` subproject1
    ` subproject2
 ` projects
    ` example1

```

where `example1` has dependencies to `monorepo/subproject1` you may like to install vendors, while keeping only a single copy of your subproject1. Symlinks aka. [Path-Repositories](https://getcomposer.org/doc/05-repositories.md#path) to the rescue!

This also allows you to use the dependency before even publishing it to an external, without manually adding the path-repository to your composer.json

### Usage

[](#usage)

`composer global require meeva/composer-monorepo-builder-path-plugin`

That's all. Nothing to configure. It detects your monorepo\_dir by traversing up to your merged composer.json, and search all other composer.json in subdirectories (vendor excluded).

Now if you do `composer require monorepo/subproject1` within the path `monorepo_dir/projects/example1` it should use a path-symlink to install the dependency to `monorepo_dir/projects/example1/vendor`.

#### Deployment

[](#deployment)

Assuming you're gonna build a deploy version of your Project, this plugin is disabled if you're using `--no-dev`.

Also you can use the environment-variable `COMPOSER_MONOREPO` with one of these values:

- `force` -> enable, even if `--no-dev` is present
- `skip` -> disabled
- *anything else* (default) -> enabled, `unless --no-dev` is present

### Known Caveats

[](#known-caveats)

- Performance is bad on Windows, but I'm sure you're used to it by now

###  Health Score

37

—

LowBetter than 83% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity37

Limited adoption so far

Community11

Small or concentrated contributor base

Maturity65

Established project with proven stability

 Bus Factor1

Top contributor holds 66.7% 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 ~246 days

Recently: every ~340 days

Total

7

Last Release

1208d ago

Major Versions

v0.4 → v2.02021-04-23

### Community

Maintainers

![](https://www.gravatar.com/avatar/3a27c82c890ca7f2b378ddb70e141dff634d8305cd8586848cc7547c55cb8819?d=identicon)[possi](/maintainers/possi)

---

Top Contributors

[![possi](https://avatars.githubusercontent.com/u/1308937?v=4)](https://github.com/possi "possi (2 commits)")[![drainerlight](https://avatars.githubusercontent.com/u/28043807?v=4)](https://github.com/drainerlight "drainerlight (1 commits)")

###  Code Quality

Code StylePHP CS Fixer

### Embed Badge

![Health badge](/badges/meeva-composer-monorepo-builder-path-plugin/health.svg)

```
[![Health](https://phpackages.com/badges/meeva-composer-monorepo-builder-path-plugin/health.svg)](https://phpackages.com/packages/meeva-composer-monorepo-builder-path-plugin)
```

###  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.3M16](/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.9M446](/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)