PHPackages                             wp-jazz/coding-standards - 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. [PSR &amp; Standards](/categories/psr-standards)
4. /
5. wp-jazz/coding-standards

ActivePhpcodesniffer-standard[PSR &amp; Standards](/categories/psr-standards)

wp-jazz/coding-standards
========================

The WordPress coding standards applied to all WP Jazz projects.

0663

Since Mar 15Pushed 3y ago1 watchersCompare

[ Source](https://github.com/wp-jazz/coding-standards)[ Packagist](https://packagist.org/packages/wp-jazz/coding-standards)[ RSS](/packages/wp-jazz-coding-standards/feed)WikiDiscussions main Synced 1mo ago

READMEChangelogDependenciesVersions (1)Used By (0)

📝 Coding Standards
==================

[](#-coding-standards)

The WordPress coding standards applied to all WP Jazz projects.

Provides a set of rulesets and extensions for:

- [EditorConfig](https://editorconfig.org/) — Maintain consistent coding styles between different editors.
- [PHP\_CodeSniffer](https://github.com/squizlabs/PHP_CodeSniffer) — PHP coding linter.
- [PHPStan](https://phpstan.org/) — PHP static analysis tool.
- [Psalm](https://psalm.dev/) — PHP static analysis tool.

> These coding standards are heavily based on, and extend, [Human Made Coding Standards](https://github.com/humanmade/coding-standards).

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

[](#installation)

```
composer require --dev wp-jazz/coding-standards
```

This package will install supported versions of PHPCS, PHPStan, and Psalm.

See the [examples](examples) directory for boilerplate configuration files.

Using PHPCS
-----------

[](#using-phpcs)

Our PHPCS ruleset extends the Human Made coding standards for PHP and WordPress.

Run the following command to run the standards checks:

```
./vendor/bin/phpcs --standard=vendor/wp-jazz/coding-standards .
```

Or include the following in your `phpcs.xml`:

```

```

The PHPCS ruleset is based upon:

- [Human Made Coding Standards](https://github.com/humanmade/coding-standards)
    - [PHPCompatibilityWP](https://github.com/PHPCompatibility/PHPCompatibilityWP)
    - [PSR-2-R](https://github.com/php-fig-rectified/psr2r-sniffer)
        - [Spryker Code Sniffer](https://github.com/spryker/code-sniffer)
        - [Slevomat Coding Standard](https://github.com/slevomat/coding-standard)
    - [WordPress Coding Standards](https://github.com/WordPress/WordPress-Coding-Standards)
    - [WordPress VIP Coding Standards](https://github.com/Automattic/VIP-Coding-Standards)

With customisations, exclusions, and additions to match our style.

Using PHPStan
-------------

[](#using-phpstan)

Run the following command to run the static analysis:

```
./vendor/bin/phpstan analyze -c vendor/szepeviktor/phpstan-wordpress/extension.neon .
```

Make PHPStan find it automatically using [phpstan/extension-installer](https://github.com/phpstan/extension-installer):

```
composer require --dev phpstan/extension-installer
```

Or manually include it in your `phpstan.neon`:

```
includes:
  - vendor/szepeviktor/phpstan-wordpress/extension.neon
```

See the [szepeviktor/phpstan-wordpress](https://github.com/szepeviktor/phpstan-wordpress) package, by Viktor Szépe, for more information on configuring PHPStan.

Using Psalm
-----------

[](#using-psalm)

```
./vendor/bin/psalm -c vendor/wp-jazz/coding-standards/psalm.xml.dist .
```

Use Psalm to enable the plugin:

```
./vendor/bin/psalm-plugin enable humanmade/psalm-plugin-wordpress
```

Or manually include it in your `psalm.xml`:

```

```

See the [humanmade/psalm-plugin-wordpress](https://github.com/humanmade/psalm-plugin-wordpress) package, by Human Made, for more information on configuring Psalm.

Using ESLint
------------

[](#using-eslint)

We recommend using the Human Made coding standards for JavaScript which uses [ESLint](https://eslint.org/).

```
npx install-peerdeps --dev @humanmade/eslint-config@latest
```

See the [@humanmade/eslint-config package README](https://github.com/humanmade/coding-standards/blob/master/packages/eslint-config-humanmade/readme.md)for more information on configuring ESLint.

Using Stylelint
---------------

[](#using-stylelint)

We recommend using the Human Made coding standards for CSS and SCSS which uses [Stylelint](https://stylelint.io/).

```
npm install --save-dev stylelint @humanmade/stylelint-config
```

See the [@humanmade/stylelint package README](https://github.com/humanmade/coding-standards/blob/master/packages/stylelint-config/readme.md)for more information on configuring Stylelint.

###  Health Score

17

—

LowBetter than 6% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity13

Limited adoption so far

Community7

Small or concentrated contributor base

Maturity23

Early-stage or recently created project

 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.

### Community

Maintainers

![](https://www.gravatar.com/avatar/0a4f39523b4b2837562ba0848a0327b8d340118d1ba87cb0f5d59b1d5cb6beba?d=identicon)[mcaskill](/maintainers/mcaskill)

---

Top Contributors

[![mcaskill](https://avatars.githubusercontent.com/u/29353?v=4)](https://github.com/mcaskill "mcaskill (9 commits)")

### Embed Badge

![Health badge](/badges/wp-jazz-coding-standards/health.svg)

```
[![Health](https://phpackages.com/badges/wp-jazz-coding-standards/health.svg)](https://phpackages.com/packages/wp-jazz-coding-standards)
```

###  Alternatives

[phpdocumentor/type-resolver

A PSR-5 based resolver of Class names, Types and Structural Element Names

9.2k719.5M166](/packages/phpdocumentor-type-resolver)[pimple/pimple

Pimple, a simple Dependency Injection Container

2.7k130.5M1.4k](/packages/pimple-pimple)[league/container

A fast and intuitive dependency injection container.

86387.8M343](/packages/league-container)[stella-maris/clock

A pre-release of the proposed PSR-20 Clock-Interface

7947.5M2](/packages/stella-maris-clock)[wptrt/wpthemereview

PHP\_CodeSniffer rules (sniffs) to verify theme compliance with the rules for theme hosting on wordpress.org

217736.5k29](/packages/wptrt-wpthemereview)[inpsyde/modularity

Modular PSR-11 implementation for WordPress plugins, themes or libraries.

54383.3k3](/packages/inpsyde-modularity)

PHPackages © 2026

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