PHPackages eighteen73/wordpress-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. [Utility & Helpers](/categories/utility) 4. / 5. eighteen73/wordpress-coding-standards ActivePhpcodesniffer-standard[Utility & Helpers](/categories/utility) eighteen73/wordpress-coding-standards ===================================== Modestly opinionated PHPCS configuration for WordPress. V2.0.1(2y ago)11.4k↑16.7%[1 issues](https://github.com/eighteen73/wordpress-coding-standards/issues)12MITJavaScript Since Jul 11Pushed 5mo ago3 watchersCompare [ Source](https://github.com/eighteen73/wordpress-coding-standards)[ Packagist](https://packagist.org/packages/eighteen73/wordpress-coding-standards)[ RSS](/packages/eighteen73-wordpress-coding-standards/feed)WikiDiscussions main Synced 1mo ago READMEChangelog (10)Dependencies (4)Versions (6)Used By (12) eighteen73 WordPress coding standards ===================================== [](#eighteen73-wordpress-coding-standards) eighteen73 coding standards for WordPress projects. Setup ----- [](#setup) Each ruleset is available individually via Composer or NPM. To install the needed ruleset, use one of the following commands: - PHPCS: `composer require --dev eighteen73/wordpress-coding-standards` - ESLint: `npx install --save-dev @eighteen73/eslint-config-wordpress` - stylelint: `npm install --save-dev @eighteen73/stylelint-config-wordpress` Using PHPCS ----------- [](#using-phpcs) Run the following command to run the standards checks: ``` vendor/bin/phpcs --standard=vendor/eighteen73/wordpress-coding-standards . ``` We use the [DealerDirect phpcodesniffer-composer-installer](https://github.com/Dealerdirect/phpcodesniffer-composer-installer) package to handle `installed_paths` for PHPCS when first installing the eighteen73 ruleset. If you an error such as `ERROR: Referenced sniff "WordPress-Core" does not exist`, delete the `composer.lock` file and `vendor` directories and re-install Composer dependencies. The final `.` here specifies the files you want to test; this is typically the current directory (`.`), but you can also selectively check files or directories by specifying them instead. ### Included Checks [](#included-checks) The phpcs standard is based upon the `WordPress-VIP` standard from [WordPress Coding Standards](https://github.com/WordPress-Coding-Standards/WordPress-Coding-Standards), with [customisation and additions](Eighteen73-WordPress-Default/ruleset.xml) to match our style guide. ### Excluding/Disabling Checks [](#excludingdisabling-checks) Rules can be disabled inline. [phpcs rules can be disabled](https://github.com/squizlabs/PHP_CodeSniffer/wiki/Advanced-Usage#ignoring-parts-of-a-file) with a `// @codingStandardsIgnoreLine` comment, and [ESLint rules can be disabled](http://eslint.org/docs/user-guide/configuring#disabling-rules-with-inline-comments) with a `/* eslint disable ... */` comment. To find out what these codes are, specify `-s` when running `phpcs`, and the code will be output as well. You can specify a full code, or a partial one to disable groups of errors. Using ESLint ------------ [](#using-eslint) The ESLint package contains an [ESLint](https://eslint.org/) configuration which you can use to validate your JavaScript code style. While it is possible to run ESLint via phpcs, we recommend you install and use eslint via npm directly. See [the `@eighteen73/eslint-config-wordpress` package README](packages/eslint-config-wordpress/README.md) for more information on configuring ESLint to use the eighteen73 coding standards. To integrate the eighteen73 rules into your project, add a `.eslintrc` file and extend these rules. You can also add your own rules and overrides for further customization. ``` { "extends": "@eighteen73/eslint-config-wordpress" "rules": { ... } } ``` Using stylelint --------------- [](#using-stylelint) The stylelint package contains a [stylelint](https://stylelint.io/) configuration which you can use to validate your CSS and SCSS code style. We recommend you install and use stylelint via npm directly. See [the `@eighteen73/stylelint-config-wordpress` package README](packages/stylelint-config/README.md) for more information on configuring stylelint to use the eighteen73 coding standards. To integrate the eighteen73 rules into your project, add a `.stylelintrc` file and extend these rules. You can also add your own rules and overrides for further customization. ``` { "extends": "@eighteen73/stylelint-config-wordpress", "rules": { ... } } ``` ### Health Score 30 — LowBetter than 64% of packages Maintenance29 Infrequent updates — may be unmaintained Popularity20 Limited adoption so far Community17 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 Every ~23 days Total 4 Last Release 973d ago Major Versions V1.0.1 → V2.0.02023-09-18 ### Community Maintainers ![](https://www.gravatar.com/avatar/892c0716ab606189211e31c70047104e48067d22fc385770b193d89e8a056164?d=identicon)[brettsmason](/maintainers/brettsmason) --- Top Contributors [![brettsmason](https://avatars.githubusercontent.com/u/73229?v=4)](https://github.com/brettsmason "brettsmason (31 commits)") ### Embed Badge ![Health badge](/badges/eighteen73-wordpress-coding-standards/health.svg) ``` [![Health](https://phpackages.com/badges/eighteen73-wordpress-coding-standards/health.svg)](https://phpackages.com/packages/eighteen73-wordpress-coding-standards) ``` ### Alternatives [humanmade/coding-standards Human Made Coding Standards 161424.0k49](/packages/humanmade-coding-standards)[woocommerce/woocommerce-sniffs WooCommerce sniffs 496.8M42](/packages/woocommerce-woocommerce-sniffs)[yoast/yoastcs PHP\_CodeSniffer rules for Yoast projects 221.1M29](/packages/yoast-yoastcs)[syde/phpcs Syde PHP coding standards for WordPress projects. 1019.7k7](/packages/syde-phpcs)[bjornjohansen/wp-pre-commit-hook Pre-commit hook for WordPress projects 118.8k3](/packages/bjornjohansen-wp-pre-commit-hook) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)