PHPackages                             netherphp/world - 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. [Framework](/categories/framework)
4. /
5. netherphp/world

ActiveLibrary[Framework](/categories/framework)

netherphp/world
===============

A meta package to include all the things.

v3.0.1(8y ago)0244BSD-2-ClausePHP >=7.1.0

Since Jul 30Pushed 8y agoCompare

[ Source](https://github.com/netherphp/world)[ Packagist](https://packagist.org/packages/netherphp/world)[ RSS](/packages/netherphp-world/feed)WikiDiscussions master Synced 4d ago

READMEChangelogDependencies (12)Versions (10)Used By (0)

Nether World (Current Version: v3.y.z)
======================================

[](#nether-world-current-version-v3yz)

A meta package to include all the things. This package will require verisons that do not break backwards compat from the previous release of this package. This makes sense in my head but let me elaborate just in case.

About Versioning
================

[](#about-versioning)

Do not just copy this line. Note the current version series above.

```
require { "netherphp/world": "^x.y.z" }

```

This will include the entire Nether stack and allow the individual components of the stack to update as is. This does not nessessarily mean that all of the Nether packages are in the 1.0.x zone. For example, as of this writing Surface and OneScript are already in the 1.1.x zone.

The next time THIS package updates it will be 1.1.0 or 2.0.0 - so composer update will still be safe for you because the way "^1.0.0" works, it will not allow 1.1.0 or 2.0.0. Patch releases (0.0.x) will happen automatically for you on composer update. Minor releases (0.x.x) will not happen automatically against "^1.0.0" so when Nether World goes to 1.1.8 or whatever, you will need to update your composer to "^1.1.0" if you are ready to deal with the BC changes.

I don't know if that made sense. But if you are using Nether World to just get all the things use the ^#.#.0 syntax and you will always stay up to date with each component without backwards compat breakages.

###  Health Score

28

—

LowBetter than 54% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity11

Limited adoption so far

Community6

Small or concentrated contributor base

Maturity64

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

Recently: every ~130 days

Total

9

Last Release

3191d ago

Major Versions

v1.1.0 → v2.0.02016-01-25

v2.2.1 → v3.0.02017-08-18

PHP version history (3 changes)v1.0.0PHP >=5.4.0

v2.0.0PHP >=7.0.0

v3.0.1PHP >=7.1.0

### 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 (24 commits)")

---

Tags

phpframeworknetherpony

### Embed Badge

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

```
[![Health](https://phpackages.com/badges/netherphp-world/health.svg)](https://phpackages.com/packages/netherphp-world)
```

PHPackages © 2026

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