PHPackages                             netherphp/composer-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 &amp; Helpers](/categories/utility)
4. /
5. netherphp/composer-plugin

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

netherphp/composer-plugin
=========================

Adds some features to Composer via its plugin system.

v1.0.1(4y ago)084MITPHPPHP ^7.0 || ^8.0

Since May 19Pushed 4y ago1 watchersCompare

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

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

Nether Composer Plugin
======================

[](#nether-composer-plugin)

Add features to Composer via a plugin.

New Features
============

[](#new-features)

Update Warning / Block
----------------------

[](#update-warning--block)

If **composer-update-warning.txt** exists in the project along side the **composer.json** file then any attempts to run `composer update` will fail, citing the contents of that text file.

```
bob@mcp:/opt/web-prod git:master $ composer update

[Exception]
Why are you doing this on production?
Use `composer install` instead.

```

Handy because maybe you know of an incoming incompability that the version constraints are not going to juggle and you just not prepared to deal with it. Or maybe you keep typing `composer update` on production like an idiot instead of `composer install`.

You can just create **composer-update-warning.txt** in your project root with any text editor you want. Additionally there is a new Composer command for doing it.

```
composer set-update-warning "bruh you aint ready for this"

```

To allow updating again simply empty the file, delete the file, or use `composer set-update-warning` with no message and Composer will delete it for you. It is just a boring text file that way anyone who wants to see why there is an update warning without actually trying can also be informed.

Note, when using `set-update-warning` the quotes are totes required.

Install
=======

[](#install)

`composer require netherphp/composer-plugin`

###  Health Score

27

—

LowBetter than 49% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity9

Limited adoption so far

Community7

Small or concentrated contributor base

Maturity61

Established project with proven stability

 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 ~1 days

Total

4

Last Release

1820d ago

Major Versions

v0.0.2 → v1.0.02021-05-24

### Community

Maintainers

![](https://www.gravatar.com/avatar/b64ee49e86efa67a7de4afdc42c2686460d1e46ac7eac7e6ccfa6407ec7d979a?d=identicon)[bobmagicii](/maintainers/bobmagicii)

---

Top Contributors

[![bobmagicii](https://avatars.githubusercontent.com/u/881944?v=4)](https://github.com/bobmagicii "bobmagicii (10 commits)")

### Embed Badge

![Health badge](/badges/netherphp-composer-plugin/health.svg)

```
[![Health](https://phpackages.com/badges/netherphp-composer-plugin/health.svg)](https://phpackages.com/packages/netherphp-composer-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)
