PHPackages                             buseet/wunderland - 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. buseet/wunderland

ActiveLibrary

buseet/wunderland
=================

1.1.1(5y ago)01.5k[1 PRs](https://github.com/TheGeekyM/wunderland/pulls)MITPHPCI passing

Since Apr 13Pushed 3mo ago2 watchersCompare

[ Source](https://github.com/TheGeekyM/wunderland)[ Packagist](https://packagist.org/packages/buseet/wunderland)[ RSS](/packages/buseet-wunderland/feed)WikiDiscussions master Synced today

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

Buseet - The Wunderland
=======================

[](#buseet---the-wunderland)

Project scope
-------------

[](#project-scope)

Currently we have a live backend API for buseet and we're in a middle of an operation/process to refactor what we have as a multi-stage process.

Wunderland will contain all the logic needed

You can install the package via composer:

```
composer require buseet/wunderland
```

Architecture
------------

[](#architecture)

Currently Wunderland follows hexagonal architecture. Meaning that if it needs to communicate with any other external dependency(eg: database) it will define interfaces for it and the actual implementation for it will be in the legacy system. In other worlds, the goal is to make the legacy system serve as an application layer that has the integration to db connection/qyery, logging, analytics,.. Wunderland will hold all the business logic. Mainly, Wunderland will be **a composer package** that is imported to the legacy system.

The diagram below will show you how this will work.

[![architecture](docs/wunderland-architecture.jpg)](docs/wunderland-architecture.jpg)

Rollout
-------

[](#rollout)

Wunderland production release will be handled as phased rollout. Meaning that we'll rely on a feature-flag to enable the old system to start using wunderland. This will make it easier for the development team to rollout/back any new integration.

For example: we might need to rollout wunderland to process the booking requests only. We'll have a feature flag that will decide if this request could be processed by wunderland or the legacy system. Then we might allow the feature flag to enabled wunderland to serve 10% of the requests. Then we monitor the requests if it went fine we keep increasing it. At some point we'll be sure that wunderland is working as expected so Wunderland will be service 100% of the requests.

The diagram below will show you how this will work. [![rollout](docs/wunderland-phased-migration.jpg)](docs/wunderland-phased-migration.jpg)

### Project name (Wunderland)

[](#project-name-wunderland)

It was named after a German operation happened in the WWII. In brief, Germans knew that soviet ships will need to hide. Mainly soviet ships choose to hide near their ice breakers near the Arctic ocean. The German fleet went there and found nothing, they never lost hope and kept looking and kept searching until they found soviet ships, steamers and cargoes and they sunk them all. Wunderland happened when the Germans were almost losing hope but it was amazing push against the allied troops.

###  Health Score

38

—

LowBetter than 85% of packages

Maintenance54

Moderate activity, may be stable

Popularity15

Limited adoption so far

Community10

Small or concentrated contributor base

Maturity61

Established project with proven stability

 Bus Factor1

Top contributor holds 52.6% 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 ~4 days

Total

3

Last Release

2125d ago

Major Versions

0.1 → 1.12020-07-16

### Community

Maintainers

![](https://www.gravatar.com/avatar/969bfcf4457bc5199ca47192dfcb06c61991739f2968f748e41f4ad83e8e2df0?d=identicon)[TheGeeky](/maintainers/TheGeeky)

---

Top Contributors

[![TheGeekyM](https://avatars.githubusercontent.com/u/8965415?v=4)](https://github.com/TheGeekyM "TheGeekyM (10 commits)")[![AlaaAttya](https://avatars.githubusercontent.com/u/2943218?v=4)](https://github.com/AlaaAttya "AlaaAttya (9 commits)")

###  Code Quality

TestsPHPUnit

### Embed Badge

![Health badge](/badges/buseet-wunderland/health.svg)

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

###  Alternatives

[prestashop/prestashop

PrestaShop is an Open Source e-commerce platform, committed to providing the best shopping cart experience for both merchants and customers.

9.0k15.4k](/packages/prestashop-prestashop)[ec-cube/ec-cube

EC-CUBE EC open platform.

78527.0k1](/packages/ec-cube-ec-cube)[akeneo/pim-community-dev

Akeneo PIM, the future of catalog management is open!

1.0k614.1k81](/packages/akeneo-pim-community-dev)[open-dxp/opendxp

Content &amp; Product Management Framework (CMS/PIM)

7310.3k29](/packages/open-dxp-opendxp)[jasonroman/nba-api

PHP Library to request data from various endpoints on NBA websites

994.6k](/packages/jasonroman-nba-api)[chameleon-system/chameleon-base

The Chameleon System core.

1026.5k3](/packages/chameleon-system-chameleon-base)

PHPackages © 2026

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