WordPress/WordPress-Coding-Standards
PHP_CodeSniffer rules (sniffs) to enforce WordPress coding conventions observed · 2026-08-28
Health v2 · maintenance only
89/100
- Activity 98
- Release rhythm 71
- Longevity 100
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.
- gap_med: 123
- age_days: 5602
- days_rel: 37
- days_push: 13
- n_releases_24m: 4
Adoption not part of the score
2823 stars · 523 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded
A set of PHP_CodeSniffer rules (sniffs) that enforce WordPress coding conventions in PHP code. It integrates with PHPCS, IDEs, and CI pipelines to lint WordPress projects against official standards.
Use cases
- lint wordpress plugin code against coding standards
- enforce wordpress coding conventions in ci
- check php code style for wordpress themes
- run phpcs with wordpress ruleset
- integrate wordpress standards into ide
When to choose
- developing WordPress plugins, themes, or core contributions
- wanting automated style enforcement in CI or editor
- need official WordPress PHP coding conventions
When to avoid
- linting non-WordPress PHP projects
- needing full static analysis beyond style/convention checks
Facets
library · maturity active
linter developer-tools testing developer-tools web-development cms php cli cross-platform phpcs coding-standards wordpress code-quality static-analysis sniffs
1 source
- readme: https://github.com/WordPress/WordPress-Coding-Standards · fetched 2026-08-28 · a530ed030bf2
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| WordPress/WordPress-Coding-Standards | main | 89 |
For agents
markdown · JSON · MCP: product_card(name="WordPress/WordPress-Coding-Standards")
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem