PHPackages                             mareknocon/composer-stability-patterns - 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. mareknocon/composer-stability-patterns

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

mareknocon/composer-stability-patterns
======================================

Specify Composer's minimum stability using patterns

v0.0.1(3y ago)024MITPHPPHP ^7.4 || ^8.0

Since Feb 11Pushed 3y ago1 watchersCompare

[ Source](https://github.com/mnocon/composer-stability-patterns)[ Packagist](https://packagist.org/packages/mareknocon/composer-stability-patterns)[ RSS](/packages/mareknocon-composer-stability-patterns/feed)WikiDiscussions main Synced 1mo ago

READMEChangelogDependencies (8)Versions (2)Used By (0)

Composer Stability Patterns
===========================

[](#composer-stability-patterns)

Description
-----------

[](#description)

This plugin allows you to specify Composer's minimum stability using more granular patterns, similar as the `preferred-install` and `allow-plugins` options do.

Instalation
-----------

[](#instalation)

The plugin needs to be active during the `pre-pool-create` event - meaning that in order to work it needs to be already installed and activated before that. That's why global installation is needed:

```
composer global require mareknocon/composer-stability-patterns
```

Examples
--------

[](#examples)

Specify the patterns and their stability level in the `exta` section in `composer.json` file:

```
    "extra": {
        "minimum-stability": {
            "my-organization/specific-package": "stable",
            "my-organization/*": "dev",
            "partner-organization/*": "rc",
            "*": "stable"
        }
    }
```

Doc
---

[](#doc)

Together with this plugin there are three options to specify minimum stability, which are resolved in the following order:

1. Package stability level

    Directly specified stability (`@dev`, `@alpha`, `@beta`, `@RC`) for a package will be used.
2. Granular stability level

    If package name matches one of the specified patterns then the stability level of the first matching pattern will be used
3. Global stability level

###  Health Score

20

—

LowBetter than 14% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity6

Limited adoption so far

Community7

Small or concentrated contributor base

Maturity40

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

Unknown

Total

1

Last Release

1183d ago

### Community

Maintainers

![](https://www.gravatar.com/avatar/55190e7571f100d9d9a587cb28210575e1065275933cb691d79a58430432a9cf?d=identicon)[mnocon](/maintainers/mnocon)

---

Top Contributors

[![mnocon](https://avatars.githubusercontent.com/u/10993858?v=4)](https://github.com/mnocon "mnocon (7 commits)")

###  Code Quality

TestsPHPUnit

Static AnalysisPHPStan

Code StylePHP CS Fixer

Type Coverage Yes

### Embed Badge

![Health badge](/badges/mareknocon-composer-stability-patterns/health.svg)

```
[![Health](https://phpackages.com/badges/mareknocon-composer-stability-patterns/health.svg)](https://phpackages.com/packages/mareknocon-composer-stability-patterns)
```

###  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)