PHPackages                             byteever/byteever-sniffs - 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. byteever/byteever-sniffs

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

byteever/byteever-sniffs
========================

A comprehensive PHP\_CodeSniffer ruleset extending WordPress Coding Standards with ByteEver-specific conventions for modern PHP development

v1.1.3(11mo ago)15.6k↓50%1GPL-3.0-onlyShell

Since Feb 18Pushed 11mo ago1 watchersCompare

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

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

ByteEver Sniffs
===============

[](#byteever-sniffs)

A comprehensive PHP\_CodeSniffer ruleset that extends WordPress Coding Standards with ByteEver-specific conventions for modern PHP development.

Features
--------

[](#features)

- 🎯 **WordPress-First**: Built on top of WordPress Coding Standards (WPCS) 3.1.0
- 🐘 **PHP Compatibility**: Supports PHP 7.4 - 8.5 with PHPCompatibility checks
- ⚡ **Performance**: Configured for parallel processing with 8 threads
- 🎨 **Sensible Defaults**: Pre-configured with practical exclusions for real-world development
- 📝 **Tab Indentation**: Enforces consistent tab-based indentation
- 🔧 **Customizable**: Easy to extend and override rules per project

What's Included
---------------

[](#whats-included)

### Base Standards

[](#base-standards)

- **WordPress**: Complete WordPress coding standards
- **WordPress-Extra**: Additional WordPress-specific rules
- **WordPress-Docs**: Documentation standards
- **PHPCompatibilityWP**: WordPress-specific PHP compatibility checks

### ByteEver Customizations

[](#byteever-customizations)

- Tab-based indentation (1 tab = 1 indent level)
- Space inside parentheses for better readability
- Relaxed file naming requirements
- Allowance for shorthand array syntax `[]`
- Sensible exclusions for database queries and nonce verification
- Comment and doc comment tokens ignored in indentation checks

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

[](#installation)

Install via Composer:

```
composer require byteever/byteever-sniffs
```

The package will automatically:

- Install PHP\_CodeSniffer and required dependencies
- Register the `ByteEver-Default` standard
- Set it as the default standard for your project

Usage
-----

[](#usage)

### Command Line

[](#command-line)

#### Quick Check

[](#quick-check)

```
vendor/bin/phpcs .
```

#### Using Composer Script

[](#using-composer-script)

```
composer run phpcs
```

#### Custom Configuration

[](#custom-configuration)

```
vendor/bin/phpcs --standard=ByteEver-Default path/to/files
```

### IDE Integration

[](#ide-integration)

For better IDE integration, create a `.phpcs.xml.dist` file in your project root:

```

    Project-specific coding standards based on ByteEver defaults.

    src/
    inc/

    vendor/
    node_modules/
    *.min.js

```

### Continuous Integration

[](#continuous-integration)

Add to your CI workflow:

```
# GitHub Actions example
- name: PHP CodeSniffer
  run: composer run phpcs
```

Configuration Details
---------------------

[](#configuration-details)

### PHP Version Support

[](#php-version-support)

- **Minimum**: PHP 7.4
- **Maximum**: PHP 8.5
- **Compatibility**: Uses PHPCompatibilityWP for WordPress-specific compatibility checks

### Key Rules Applied

[](#key-rules-applied)

- WordPress Coding Standards (with sensible exclusions)
- Tab indentation (1 tab per indent level)
- Space inside parentheses for readability
- Superfluous whitespace detection
- PHP compatibility checking for WordPress

### Excluded Rules

[](#excluded-rules)

The following rules are excluded for practical development:

- File naming conventions (WordPress.Files.FileName)
- Nonce verification requirements
- Direct database query restrictions
- Global variable override prohibitions
- Some documentation capitalization requirements

Customization
-------------

[](#customization)

### Project-Level Overrides

[](#project-level-overrides)

Create a `phpcs.xml.dist` file to override or add rules:

```

    admin/ajax-handlers/*

```

### Inline Annotations

[](#inline-annotations)

Disable rules for specific code blocks:

```
// phpcs:disable WordPress.Security.NonceVerification.Missing
if ( isset( $_POST['data'] ) ) {
    // Process data without nonce check
}
// phpcs:enable WordPress.Security.NonceVerification.Missing
```

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

[](#requirements)

- PHP 7.4 or higher
- Composer
- PHP\_CodeSniffer 3.9.0 or higher

Dependencies
------------

[](#dependencies)

- `dealerdirect/phpcodesniffer-composer-installer`: ^1.0
- `phpcompatibility/phpcompatibility-wp`: ^2.1
- `wp-coding-standards/wpcs`: ^3.1.0

Contributing
------------

[](#contributing)

1. Fork the repository
2. Create a feature branch
3. Make your changes
4. Test with `composer run phpcs`
5. Submit a pull request

License
-------

[](#license)

GPL-3.0-only

Author
------

[](#author)

**Sultan Nasir Uddin**
Email:
Organization: ByteEver

---

*Part of the ByteEver development toolkit for WordPress and PHP projects.*

###  Health Score

39

—

LowBetter than 86% of packages

Maintenance52

Moderate activity, may be stable

Popularity24

Limited adoption so far

Community9

Small or concentrated contributor base

Maturity59

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 ~197 days

Recently: every ~27 days

Total

9

Last Release

333d ago

### Community

Maintainers

![](https://www.gravatar.com/avatar/888ecb9bec980eb4758575606e394842d4552fe72897e5183af8bb656035fba7?d=identicon)[sultann](/maintainers/sultann)

---

Top Contributors

[![sultann](https://avatars.githubusercontent.com/u/5239470?v=4)](https://github.com/sultann "sultann (27 commits)")

---

Tags

byteeverphpcsstandardswordpressstandardsphpcswordpressbyteever

### Embed Badge

![Health badge](/badges/byteever-byteever-sniffs/health.svg)

```
[![Health](https://phpackages.com/badges/byteever-byteever-sniffs/health.svg)](https://phpackages.com/packages/byteever-byteever-sniffs)
```

###  Alternatives

[automattic/vipwpcs

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

25510.2M145](/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)[yoast/yoastcs

PHP\_CodeSniffer rules for Yoast projects

221.1M29](/packages/yoast-yoastcs)[infinum/eightshift-coding-standards

Eightshift WordPress Coding Standards

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

WooCommerce sniffs

496.8M42](/packages/woocommerce-woocommerce-sniffs)[mayflower/mo4-coding-standard

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

17508.3k5](/packages/mayflower-mo4-coding-standard)

PHPackages © 2026

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