PHPackages                             bluehost/wp-php-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 & Standards](/categories/psr-standards)
4. /
5. bluehost/wp-php-standards

Abandoned → [newfold-labs/wp-php-standards](/?search=newfold-labs%2Fwp-php-standards)ArchivedPhpcodesniffer-standard[PSR & Standards](/categories/psr-standards)

bluehost/wp-php-standards
=========================

PHP Code Sniffer Standards for Bluehost WordPress projects.

1.1.1(3y ago)039↓100%GPL-2.0-or-later

Since Jan 7Pushed 3y ago10 watchersCompare

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

READMEChangelog (3)Dependencies (4)Versions (12)Used By (0)

WordPress PHP Standards
=======================

[](#wordpress-php-standards)

PHP Code Sniffer Standards for Bluehost WordPress projects.

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

[](#installation)

Add this Satis repository to your `composer.json` file:

```
"repositories": [
    {
      "type": "composer",
      "url": "https://bluehost.github.io/satis/"
    }
  ],
```

Run `composer require bluehost/wp-php-standards` from your project root.

Usage
-----

[](#usage)

Run `vendor/bin/phpcs . --standard=Bluehost` from your project root to check your code.

Optionally, add a script to your `composer.json` file so you can just run `composer run lint` to check your code.

```
    "scripts": {
        "lint": [
          "vendor/bin/phpcs . --standard=Bluehost"
        ],
	"clean": [
            "vendor/bin/phpcbf . --standard=Bluehost"
        ]
    }
```

Additional Notes
----------------

[](#additional-notes)

- Append the `-s` flag to see the internal names of the rules.
- Add `--runtime-set testVersion 5.2-` to check PHP version 5.2 or greater.
- Add a custom `phpcs.xml` file to your project to customize the ruleset or your desired configuration.

```

```

### Additional Documentation

[](#additional-documentation)

- [https://github.com/squizlabs/PHP\_CodeSniffer](https://github.com/squizlabs/PHP_CodeSniffer)
-
-

IDE Integration
---------------

[](#ide-integration)

Some IDE integrations of PHPCS will fail to register your ruleset since it doesn't live in your project root. In order to rectify this, place phpcs.xml at your project root:

```

```

### PHPStorm Setup

[](#phpstorm-setup)

1. Open up the preferences panel.
2. Go to "Languages & Frameworks" > "PHP" > "Code Sniffer".
3. Ensure the "Configuration" section has "Local" set in the dropdown. Click the "..." button.
4. Set the "PHP Code Sniffer path" to be "{projectRoot}/vendor/bin/phpcs" where "{projectRoot}" is the actual path of your project root.
5. Hit "OK".
6. Go to "Editor" > "Inspections" in the preference panel.
7. Click on "PHP Code Sniffer validation" under the "PHP" > "Quality tools" section.
8. Hit the refresh button next to the "Coding Standard" field on the right.
9. Select "Bluehost" from the dropdown.
10. Hit "OK" to exit the preferences panel.

###  Health Score

30

—

LowBetter than 65% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity8

Limited adoption so far

Community14

Small or concentrated contributor base

Maturity67

Established project with proven stability

 Bus Factor1

Top contributor holds 72.2% 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 ~206 days

Recently: every ~0 days

Total

9

Last Release

1026d ago

### Community

Maintainers

![](https://www.gravatar.com/avatar/2423d8916934a39dcd409d36c9d305cb87026c8632b9479508482576045fed69?d=identicon)[bhwpteam](/maintainers/bhwpteam)

![](https://www.gravatar.com/avatar/7598edcaf9b4481aa6d7a5533bbe08cf6937d12cb09aa3d318c2636a482fbbeb?d=identicon)[nvkattacker](/maintainers/nvkattacker)

---

Top Contributors

[![wpscholar](https://avatars.githubusercontent.com/u/890951?v=4)](https://github.com/wpscholar "wpscholar (13 commits)")[![0aveRyan](https://avatars.githubusercontent.com/u/9565066?v=4)](https://github.com/0aveRyan "0aveRyan (3 commits)")[![circlecube](https://avatars.githubusercontent.com/u/698049?v=4)](https://github.com/circlecube "circlecube (2 commits)")

---

Tags

codesniffer-ruleswordpress

### Embed Badge

![Health badge](/badges/bluehost-wp-php-standards/health.svg)

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

###  Alternatives

[yoast/yoastcs

PHP\_CodeSniffer rules for Yoast projects

221.1M29](/packages/yoast-yoastcs)[automattic/vipwpcs

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

25510.2M144](/packages/automattic-vipwpcs)[wptrt/wpthemereview

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

217736.5k29](/packages/wptrt-wpthemereview)[mayflower/mo4-coding-standard

PHP CodeSniffer ruleset implementing the MO4 coding standards extending the Symfony coding standards.

17508.3k5](/packages/mayflower-mo4-coding-standard)[infinum/eightshift-coding-standards

Eightshift WordPress Coding Standards

1785.2k3](/packages/infinum-eightshift-coding-standards)

PHPackages © 2026

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