PHPackages                             hurah/hurah-installer - 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. hurah/hurah-installer

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

hurah/hurah-installer
=====================

Installer scripts for Hurah!

v1.0.6(5y ago)0187[1 PRs](https://github.com/antonboutkam/hurah-installer/pulls)7MITPHPPHP >=7.4

Since Jan 4Pushed 4y ago1 watchersCompare

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

READMEChangelogDependencies (5)Versions (4)Used By (7)

Hurah installer
===============

[](#hurah-installer)

This package contains a composer plugin that manages the installation of other packages into the [Novum innovation app](https://docs.demo.novum.nu). All package types are treated as a plugin. The "type" field inside composer.json tells the package what type of plugin we have and how to treat it. These are the types of plugin

Core
----

[](#core)

Contains all the code that other componens depend on. Autoloading happens from the vendor directory but a symlink is created inside a hidden folder called `.system`. When other components or plugins are installed, they will be symlinked inside this system folder also. This is required for autoloading and code generation.

```
{
    "type" : "novum-core"
}
```

Site
----

[](#site)

This package type represents a normal website. On installation a folder called `public/` is created and symlinked to the original installation directory in the vendor folder. Another symlink is created in the `.system/public_html/` folder.

```
{
    "type" : "novum-site"
}
```

Api
---

[](#api)

The API type works the same as the site type but has some different dependencies, hence the distinction.

```
{
    "type": "novum-api"
}
```

Domain
------

[](#domain)

A domain type plugin contains all the information that is needed to bootstrap your specific application. This includes a database definition file, migration scrips, style information for the admin panel, images that are to be used in various places etc.

```
{
    "type" : "novum-domain"
}
```

Admin module
------------

[](#admin-module)

The core system comes with an admin panel that has a few modules that are included by default. For instance a `User` module that allows you to manage user accounts. Other modules need to be installed via composer.

```
{
    "type" : "novum-domain"
}
```

Installation flow
=================

[](#installation-flow)

When the installer activates for any kind of plugin it checks the folder structure and creates all the directories needed to run the system. The user will see only the directories relevant for his or her project. Inside the `.system` folder a tree of the actual project is assembled.

###  Health Score

27

—

LowBetter than 49% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity11

Limited adoption so far

Community14

Small or concentrated contributor base

Maturity55

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

Every ~0 days

Total

2

Last Release

1951d ago

### Community

Maintainers

![](https://www.gravatar.com/avatar/2d25a530c37fb5125ca911ea38a30fbbfa3db297c73c36bc70f517efdb2c5378?d=identicon)[antonboutkam](/maintainers/antonboutkam)

---

Top Contributors

[![antonboutkam](https://avatars.githubusercontent.com/u/27406772?v=4)](https://github.com/antonboutkam "antonboutkam (158 commits)")

###  Code Quality

TestsPHPUnit

### Embed Badge

![Health badge](/badges/hurah-hurah-installer/health.svg)

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

###  Alternatives

[roave/backward-compatibility-check

Tool to compare two revisions of a public API to check for BC breaks

5953.3M55](/packages/roave-backward-compatibility-check)[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.3M14](/packages/vaimo-composer-patches)[magento/magento-composer-installer

Composer installer for Magento modules

7523.3M315](/packages/magento-magento-composer-installer)[drupal/core-composer-scaffold

A flexible Composer project scaffold builder.

5341.9M440](/packages/drupal-core-composer-scaffold)[drupal/core-project-message

Adds a message after Composer installation.

2122.6M172](/packages/drupal-core-project-message)[drupol/composer-packages

Composer Packages is a Composer plugin for getting information about installed packages in your project.

32274.0k1](/packages/drupol-composer-packages)

PHPackages © 2026

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