PHPackages                             cierrateam/cierra-qa - 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. [Testing & Quality](/categories/testing)
4. /
5. cierrateam/cierra-qa

ActiveLibrary[Testing & Quality](/categories/testing)

cierrateam/cierra-qa
====================

Cierra quality assurance (qa) tools

v0.0.3(5y ago)03.6kMITPHPPHP ^7.3|^8.0

Since Jan 22Pushed 5y ago1 watchersCompare

[ Source](https://github.com/cierrateam/cierra-qa)[ Packagist](https://packagist.org/packages/cierrateam/cierra-qa)[ RSS](/packages/cierrateam-cierra-qa/feed)WikiDiscussions main Synced 1mo ago

READMEChangelog (2)Dependencies (5)Versions (6)Used By (0)

About Cierra QA
---------------

[](#about-cierra-qa)

Cierra QA (quality assurance) is a simple package that includes code quality tools in your project.
QA-Tools that will be integrated into your project:

- [PHP\_CodeSniffer](https://github.com/squizlabs/PHP_CodeSniffer)
- [Larastan](https://github.com/nunomaduro/larastan)

Furthermore, it will create a GitHub workflow file to your project under `.github/workflows` that runs QA tools on pull requests.

Installation
------------

[](#installation)

First, you may use Composer to install Cierra QA to your project:

```
composer require --dev cierrateam/cierra-qa

```

To copy the QA files to your project, you have to run the following command:

```
php artisan cierra-qa:install

```

This command will create a `.qa` folder into your root project with configuration files for `PHP_CodeSniffer` and `Larastan`.
It will also create a `code-quality.yml` file into `.github/workflows` directory and a `Makefile` into the root of your project.

❗️ Make sure to save your old `Makefile` if there exists one.

Configuration
-------------

[](#configuration)

You can update the configuration/rules files in the `.qa` for your project so that it has your standards.
❗ Please update the `php-version` in the `code-quality.yml` with the version you use for your project so that the QA-tools will use the correct PHP version on pull-request.

By default, the QA tools use the `/app` directory for analyzing. You can change the default path in the `Makefile` under `PHP_FILES`.
The default `phpstan` level is 5. You can update it also in the `Makefile` under `PHPSTAN_LEVEL`.

Usage
-----

[](#usage)

After installing and configuring the QA tools at your convenience, you can use `PHP_CodeSniffer` and `Larastan` very quickly with the `Makefile` shortcut.

- use `make phpcs` to run `PHP_CodeSniffer` for the `/app` folder.
- use `make phpstan` to run `Larastan` for the `/app` folder.

❗ You can change the path that you want to analyze and the `phpstan` level in the `Makefile` under `PHP_FILES` and `PHPSTAN_LEVEL` or provide the path directly with the `make` command: `make phpstan LEVEL=3 FILES="foo/bar/baz.php foo/bar/foo.php"`

If you don't want to analyze the whole project files under `app` you can also check only the changed files.
Run `git add .` and then `make phpcs-quick` or `make phpstan-quick`.

### PHPSTORM

[](#phpstorm)

Under `.dev/ide/phpstorm/settings` is a code styling file stored which can be imported to your PHPStorm ide under `Preferences --> Editor --> Code Style`.

###  Health Score

27

—

LowBetter than 49% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity16

Limited adoption so far

Community10

Small or concentrated contributor base

Maturity51

Maturing project, gaining track record

 Bus Factor1

Top contributor holds 85.7% 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 ~16 days

Total

3

Last Release

1900d ago

PHP version history (2 changes)v0.0.1PHP ^7.3

v0.0.2PHP ^7.3|^8.0

### Community

Maintainers

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

![](https://www.gravatar.com/avatar/70e00cab9d8cf8c28162c676e1a54c6d09a71b65593dc38a67740de70a88411b?d=identicon)[lukas-cierra](/maintainers/lukas-cierra)

---

Top Contributors

[![lukas-cierra](https://avatars.githubusercontent.com/u/69144406?v=4)](https://github.com/lukas-cierra "lukas-cierra (6 commits)")[![vittoriodev](https://avatars.githubusercontent.com/u/24706440?v=4)](https://github.com/vittoriodev "vittoriodev (1 commits)")

###  Code Quality

TestsPHPUnit

### Embed Badge

![Health badge](/badges/cierrateam-cierra-qa/health.svg)

```
[![Health](https://phpackages.com/badges/cierrateam-cierra-qa/health.svg)](https://phpackages.com/packages/cierrateam-cierra-qa)
```

###  Alternatives

[slevomat/coding-standard

Slevomat Coding Standard for PHP\_CodeSniffer complements Consistence Coding Standard by providing sniffs with additional checks.

1.5k123.5M1.8k](/packages/slevomat-coding-standard)

PHPackages © 2026

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