PHPackages                             wpengine/wpengine-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. [Testing & Quality](/categories/testing)
4. /
5. wpengine/wpengine-coding-standards

AbandonedArchivedPhpcodesniffer-standard[Testing & Quality](/categories/testing)

wpengine/wpengine-coding-standards
==================================

PHP\_CodeSniffer rules (sniffs) to enforce WP Engine coding conventions

1.0.0(5y ago)3060.0k↓50%51MITShellPHP >=5.4

Since Nov 13Pushed 1y ago48 watchersCompare

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

READMEChangelog (1)Dependencies (4)Versions (8)Used By (1)

Deprecation Notice
------------------

[](#deprecation-notice)

This project is no longer actively maintained. We recommend using the [WordPress Coding Standards](https://github.com/WordPress/WordPress-Coding-Standards) and use their [recommended configuration](https://github.com/WordPress/WordPress-Coding-Standards/blob/develop/phpcs.xml.dist.sample) for your project.

About
-----

[](#about)

WP Engine Coding Standards for WordPress

If [WordPress Coding Standards](https://make.wordpress.org/core/handbook/best-practices/coding-standards/) offer a baseline for developers to use when contributing to or extending WordPress, think of WP Engine Coding Standards as an additional layer of best practices that:

- help developers achieve greater consistency within their themes and plugins
- assist developers in meeting the requirements of a WP Engine Solution Partner
- ensure that all software listed in the WP Engine Solution Center is of the highest quality
- offer users maximum performance and security benefits when using those themes and plugins in a modern hosting environment (PHP 7+)

The information included here walks you through the process of installing and using WP Engine Coding Standards to lint your code.

Requirements
------------

[](#requirements)

WP Engine Coding Standards (WPECS) uses [Composer](https://getcomposer.org/) to install these main dependencies:

- [PHP\_Codesniffer (PHPCS)](https://github.com/squizlabs/PHP_CodeSniffer)
- [WordPress Coding Standards](https://github.com/WordPress/WordPress-Coding-Standards)
- [PHPCompatibilityWP](https://github.com/PHPCompatibility/PHPCompatibilityWP).

If you're using Homebrew on Mac, you can install Composer with: `brew install composer`. Otherwise, follow the official installation instructions for Composer.

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

[](#installation)

### Global installation

[](#global-installation)

1. Clone the repository and install the dependencies:

```
git clone git@github.com:wpengine/wpengine-coding-standards.git
cd wpengine-coding-standards
composer install
```

2. Link your coding standards to your `phpcs` installation:

```
phpcs --config-set installed_paths /path/to/wp-engine-coding-standards
```

### Install as a dependency

[](#install-as-a-dependency)

You can also install the coding standards as a dependency in your local project. Here's how

1. Add the following repository to your composer.json

```
"repositories": [
    {
      "type": "git",
      "url": "https://github.com/wpengine/wpengine-coding-standards.git"
    }
  ]
```

2. Manually add the following to `require-dev` in composer.json

```
"wpengine/wpengine-coding-standards": "dev-master"
```

3. Run `composer install` or `composer update` to ensure your project is configured.
4. You can now use `WP-Engine` or `WP-Engine-Strict` in any IDE that uses the local phpcs. If you already have a phpcs.xml in your project, simply add the following to it:

```

```

### Alternative Install (wpecs command)

[](#alternative-install-wpecs-command)

Clone or download this repository. From terminal, navigate to the download location and install WPECS globally with the following command:

```
make install

```

You will then be able to run WPECS from any directory.

Running `make install` will install WPECS dependencies and register coding standards with PHPCS.

- Note you might need to manually move the binaries to your path, or properly set path, if make fails.

Usage
-----

[](#usage)

### Command line

[](#command-line)

Run the `phpcs` command line tool on a given file or directory, for example:

```
phpcs --standard=WP-Engine wp-load.php
```

**WP-Engine Coding Standard**

*The required standard for secure WordPress development.*

`wpecs .`

**WP-Engine-Strict Coding Standard**

*The recommend standard for WP Engine authored plugins.*

`wpecs --standard="WP-Engine-Strict" .`

### Using PHPCS and WP Engine Coding Standards from within your IDE

[](#using-phpcs-and-wp-engine-coding-standards-from-within-your-ide)

While the following is based on the parent WordPress Coding Standards, simply swap out the ruleset you need for `WP-Engine` or `WP-Engine-Strict` as appropriate.

- **PhpStorm** : Please see "[PHP Code Sniffer with WordPress Coding Standards Integration](https://confluence.jetbrains.com/display/PhpStorm/WordPress+Development+using+PhpStorm#WordPressDevelopmentusingPhpStorm-PHPCodeSnifferwithWordPressCodingStandardsIntegrationinPhpStorm)" in the PhpStorm documentation.
- **Sublime Text** : Please see "[Setting up WPCS to work in Sublime Text](https://github.com/WordPress/WordPress-Coding-Standards/wiki/Setting-up-WPCS-to-work-in-Sublime-Text)" in the wiki.
- **Atom**: Please see "[Setting up WPCS to work in Atom](https://github.com/WordPress/WordPress-Coding-Standards/wiki/Setting-up-WPCS-to-work-in-Atom)" in the wiki.
- **Visual Studio**: Please see "[Setting up PHP CodeSniffer in Visual Studio Code](https://tommcfarlin.com/php-codesniffer-in-visual-studio-code/)", a tutorial by Tom McFarlin.
- **Eclipse with XAMPP**: Please see "[Setting up WPCS when using Eclipse with XAMPP](https://github.com/WordPress/WordPress-Coding-Standards/wiki/How-to-use-WPCS-with-Eclipse-and-XAMPP)" in the wiki.

### Alternative usage (wpecs)

[](#alternative-usage-wpecs)

USAGE: wpecs \[--strict\] \[phpcs-options\] Run the specified path against the WP Engine Coding Standards Attempt to fix sniffs against the WP Engine Strict Coding Standards

Results
-------

[](#results)

For help understanding errors or warnings and suggestions for troubleshooting specific issues, please refer to the full [WP Engine Coding Standards Documentation](https://github.com/wpengine/wpengine-coding-standards/wiki).

### Contributor License Agreement

[](#contributor-license-agreement)

All external contributors to WP Engine products must have a signed Contributor License Agreement (CLA) in place before the contribution may be accepted into any WP Engine codebase.

1. [Submit your name and email](https://wpeng.in/cla/)
2. 📝 Sign the CLA emailed to you
3. 📥 Receive copy of signed CLA

❤️ Thank you for helping us fulfill our legal obligations in order to continue empowering builders through headless WordPress.

###  Health Score

37

—

LowBetter than 83% of packages

Maintenance26

Infrequent updates — may be unmaintained

Popularity38

Limited adoption so far

Community24

Small or concentrated contributor base

Maturity53

Maturing project, gaining track record

 Bus Factor1

Top contributor holds 67.9% 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

2012d ago

### Community

Maintainers

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

---

Top Contributors

[![stevenkword](https://avatars.githubusercontent.com/u/1030598?v=4)](https://github.com/stevenkword "stevenkword (57 commits)")[![josephfusco](https://avatars.githubusercontent.com/u/6676674?v=4)](https://github.com/josephfusco "josephfusco (13 commits)")[![blakewilson](https://avatars.githubusercontent.com/u/5946219?v=4)](https://github.com/blakewilson "blakewilson (5 commits)")[![TeresaGobble](https://avatars.githubusercontent.com/u/50935135?v=4)](https://github.com/TeresaGobble "TeresaGobble (5 commits)")[![theodesp](https://avatars.githubusercontent.com/u/328805?v=4)](https://github.com/theodesp "theodesp (2 commits)")[![cdils](https://avatars.githubusercontent.com/u/3099408?v=4)](https://github.com/cdils "cdils (1 commits)")[![wpe-jenkins-github-admin](https://avatars.githubusercontent.com/u/33267196?v=4)](https://github.com/wpe-jenkins-github-admin "wpe-jenkins-github-admin (1 commits)")

---

Tags

marketingstandardsphpcswordpresswp-enginewpecs

### Embed Badge

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

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

###  Alternatives

[wp-coding-standards/wpcs

PHP\_CodeSniffer rules (sniffs) to enforce WordPress coding conventions

2.7k42.5M1.6k](/packages/wp-coding-standards-wpcs)[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)[phpcompatibility/phpcompatibility-wp

A ruleset for PHP\_CodeSniffer to check for PHP cross-version compatibility issues in projects, while accounting for polyfills provided by WordPress.

21830.6M587](/packages/phpcompatibility-phpcompatibility-wp)[yoast/yoastcs

PHP\_CodeSniffer rules for Yoast projects

221.1M29](/packages/yoast-yoastcs)[wptrt/wpthemereview

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

217736.5k29](/packages/wptrt-wpthemereview)[woocommerce/woocommerce-sniffs

WooCommerce sniffs

496.8M42](/packages/woocommerce-woocommerce-sniffs)

PHPackages © 2026

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