PHPackages                             backendtea/phpstan-multiple-error-formatter - 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 &amp; Quality](/categories/testing)
4. /
5. backendtea/phpstan-multiple-error-formatter

ActivePhpstan-extension[Testing &amp; Quality](/categories/testing)

backendtea/phpstan-multiple-error-formatter
===========================================

A PHPStan extension to show multiple error formats in one go

1.0.0(1y ago)17.5k↓41.4%1MITPHPPHP ^8.1

Since Nov 27Pushed 1y ago1 watchersCompare

[ Source](https://github.com/BackEndTea/phpstan-multiple-error-formatter)[ Packagist](https://packagist.org/packages/backendtea/phpstan-multiple-error-formatter)[ RSS](/packages/backendtea-phpstan-multiple-error-formatter/feed)WikiDiscussions main Synced yesterday

READMEChangelog (1)Dependencies (2)Versions (2)Used By (1)

Multiple error formatters for PHPStan
=====================================

[](#multiple-error-formatters-for-phpstan)

This project was born form a need to have multiple outputs from a PHPStan run. Its goal is to provide a way to direct outputs to multiple locations, without having to run PHPStan multiple times.

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

[](#installation)

```
composer require --dev backendtea/phpstan-multiple-error-formatter
```

If you also install [phpstan/extension-installer](https://github.com/phpstan/extension-installer) then you're all set!

 Manual installationIf you don't want to use `phpstan/extension-installer`, include extension.neon in your project's PHPStan config:

```
includes:
    - vendor/backendtea/phpstan-multiple-error-formatter/config.neon

```

Usage
-----

[](#usage)

This package provides the 'multiple' error formatter. Generally you want to use this in CI by adding the `--error-format multiple` flag.

The `multiple` error formatter wil look for the `errorFormatters.formatters` configuration option, where you can define the outputs you are looking for

This package defines the following formatters to output to a file:

- jsonFile : prints a json file
- prettyJsonFile: prints a pretty json file (with whitespaces for human readability)
- gitlabFile: outputs a file for gitlab code quality inspections

You can configure the file location it should output to with the `errorFormatters.jsonFile` and `errorFromatters.gitlabFile` configuration options:

An example where we want to write a pretty json file, a gitlab file, and output to a table in stdOut would look like this:

```
parameters:
    errorFormatters:
        formatters:
            - table
            - gitlabFile
            - prettyJsonFile
        jsonFile: %currentWorkingDirectory%/phpstan.json
        gitlabFile: %currentWorkingDirectory%/phpstan-gitlab.json
      # other config...
```

###  Health Score

33

—

LowBetter than 72% of packages

Maintenance36

Infrequent updates — may be unmaintained

Popularity26

Limited adoption so far

Community9

Small or concentrated contributor base

Maturity48

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

Unknown

Total

1

Last Release

583d ago

### Community

Maintainers

![](https://avatars.githubusercontent.com/u/14289961?v=4)[Gert de Pagter](/maintainers/BackEndTea)[@BackEndTea](https://github.com/BackEndTea)

---

Top Contributors

[![BackEndTea](https://avatars.githubusercontent.com/u/14289961?v=4)](https://github.com/BackEndTea "BackEndTea (7 commits)")

### Embed Badge

![Health badge](/badges/backendtea-phpstan-multiple-error-formatter/health.svg)

```
[![Health](https://phpackages.com/badges/backendtea-phpstan-multiple-error-formatter/health.svg)](https://phpackages.com/packages/backendtea-phpstan-multiple-error-formatter)
```

###  Alternatives

[larastan/larastan

Larastan - Discover bugs in your code without running it. A phpstan/phpstan extension for Laravel

6.5k55.4M8.4k](/packages/larastan-larastan)[phpstan/phpstan-symfony

Symfony Framework extensions and rules for PHPStan

79475.7M2.2k](/packages/phpstan-phpstan-symfony)[phpstan/phpstan-doctrine

Doctrine extensions for PHPStan

67272.8M1.4k](/packages/phpstan-phpstan-doctrine)[shipmonk/dead-code-detector

Dead code detector to find unused PHP code via PHPStan extension. Can automatically remove dead PHP code. Supports libraries like Symfony, Doctrine, PHPUnit etc. Detects dead cycles. Can detect dead code that is tested.

4853.5M91](/packages/shipmonk-dead-code-detector)[spaze/phpstan-disallowed-calls

PHPStan rules to detect disallowed method &amp; function calls, constant, namespace, attribute, property &amp; superglobal usages, with powerful rules to re-allow a call or a usage in places where it should be allowed.

33422.6M550](/packages/spaze-phpstan-disallowed-calls)[tomasvotruba/cognitive-complexity

PHPStan rules to measure cognitive complexity of your classes and methods

1635.6M288](/packages/tomasvotruba-cognitive-complexity)

PHPackages © 2026

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