Download the PHP package johnatas-x/angry-bearded without Composer

🐦 Angry bearded

This tool is a pre-configured GrumPHP for Drupal 10 & 11 projects.

The rules are intentionally strict — feel free to customize the .dist files to suit your needs.

A .editorconfig file and a Qodana template are also included.

[!CAUTION]

Since December 3, 2025, the dev-develop version of phpcompatibility requires at least squizlabs/php_codesniffer 4.0.1. If you are using an older version of this package, you may encounter a Composer conflict.

To resolve this, add the following line to the require-dev section of your composer.json:

Then run:

🔧 Included tools

• ComposerRequireChecker
• Drupal Coder
• PHP Assumptions (phpa)
• PHP Copy/Paste Detector (phpcpd)
• PHP Magic Number Detector (phpmnd)
• PHP Parallel Lint
• PHPMD
• PHPStan
  • PHPStan Banned Code
  • PHPStan Deprecation Rules
  • PHPStan Extension Installer
  • phpstan-drupal
  • Dead code detector for PHP
• PHP_CodeSniffer
  • PHP Compatibility Coding Standard for PHP CodeSniffer
  • Slevomat Coding Standard
• PhpDeprecationDetector (phpdd)
• Twigcs
  • Twig CS Fixer
• composer-normalize

🚀 Installation

[!IMPORTANT]
This tool is compatible with multiple versions of Drupal as well as multiple versions of PHP.

Choose the appropriate release for your situation using the table below:

	Drupal 10	Drupal 11	Drupal 12
PHP 8.1	1.6.*	NA	NA
PHP 8.2	1.7.*	NA	NA
PHP 8.3	2.*	2.*	NA
PHP 8.4	2.*	2.* or 3.*	NA
PHP 8.5	NA	3.*	4.*

➡️ When using drupal/core-composer-scaffold (recommended)

In most cases, you would already be using the drupal/core-composer-scaffold package if you have set up using the latest Drupal templates. This package uses core-composer-scaffold to set up configuration files in your project. To make this work, add this package name in your composer's extra.drupal-scaffold.allowed-packages section.

Now, run composer require to include the package in your application. Since the package is now allowed, the core-composer-scaffold package will copy the configuration files.

💡 More about scaffolding

As described before, this package uses drupal/core-composer-scaffold plugin to scaffold a few files to the project root. While not strictly required, it’s likely already part of your setup if you're building a Drupal site.

The scaffolding process runs during every Composer operation and may overwrite files. Only the file grumphp.yml.dist is not overwritten during later operations. If you are customizing any of the other configuration files and don't want the updates to overwrite your changes, you can override the behavior in your composer.json file. For example, to skip phpmd.xml.dist from being overwritten, add this to your composer.json:

For more details, read the "Excluding Scaffold files" section of the documentation for the core-composer-scaffold plugin.

➡️ Without drupal/core-composer-scaffold

If you're not using the scaffolding plugin, the package won't automatically copy the configuration files.

First, run composer require to include the package in your application.

If you don't already have a grumphp.yml file in your project, GrumPHP will prompt you to create one — select "No."

Then, copy all *.dist files from the package to your project root. The files copied are:

• .editorconfig.dist
• grumphp.yml.dist
• phpcs.xml.dist
• phpmd.xml.dist
• phpstan.neon.dist
• phpstan-drupal.neon.dist
• qodana.yaml.dist

[!NOTE] For deprecated checks only with PHPStan Drupal, copy phpstan-drupal-deprecated.neon.dist instead of both phpstan.neon.dist and phpstan-drupal.neon.dist.

[!TIP] To copy all files, you can run:

🚧 Usage

No additional setup is required. However, if Git hooks aren’t triggering, run: php ./vendor/bin/grumphp git:init.

For additional commands, look at grumhp's documentation.

💈 Customising

• Most customizations start by copying the grumphp.yml.dist file to your project root. Make sure you have the file.
• By default, the Drupal logo is used in successful outputs, but you can use GrumPHP's logo modifying ascii in grumphp.yml or using your own logo.

➕ Adding tasks

You can add and customize various tasks in your grumphp.yml.

Read the online documentation for GrumPHP tasks to see the tasks you can use and configure.

🛂 Forcing commit message format

To configure the commit message structure, use the git_commit_message task. For example, to enforce the commit message contains the YouTrack issue ID, use the rule as the following snippet. More options are documented online.

🚫 Disable commit banners

GrumPHP supports banners to celebrate (or scold) on your commit. This is fun, but it is possible it gets on your nerves. If you don’t want it, edit the grumphp.yml file and replace the following parameters:

You could even disable specific ones like this:

🔧 PHPUnit

PHPUnit dependencies are not bundled in this package because version management is too complex given the compatibility constraints between this tool, multiple Drupal core versions, and PHP versions.

Additionally, this tool intentionally does not include drupal/core-dev by default.

However, everything is prepared for easy integration. If you want to add PHPUnit:

1. Create an alias in your composer.json from drupal/coder 9 to 8, like :

2. Add drupal/core-dev (using the same version as your Drupal core) as a require-dev dependency ;
3. Add phpunit/phpunit (using a version compatible with your core) as a require-dev dependency ;
4. Add your phpunit.xml file at the root of your project ;
5. Enable (and configure) PHPUnit in your grumphp.yml file.

[!NOTE] Drupal Coder is included in version 9 to benefit from PHP_CS version 4.

Because Drupal Coder 9 is not compatible with any version of drupal/core-dev, it is necessary to define an alias pointing to version 8 (retro-compatibility is fully preserved); otherwise, installing drupal/core-dev will fail due to a package conflict.