PHP_CodeSniffer tokenizes PHP files and detects violations of a defined set of coding standards.
PHPCSStandards/PHP_CodeSniffer holds a health index of 87 out of 100, placing it in the Excellent band. It scores highest on Vitality (92/100) and lowest on AI Readiness (36/100). It was last updated 5 days ago. A single contributor accounts for most of its recent work.
Metrics are grouped into weighted categories on one standardized 1–100 scale. Overall starts as their weighted mean, calibrated against the distribution of the public record so bands carry percentile meaning; when public evidence triggers the High-Risk Jurisdiction Policy, the rating is adjusted and receives an At Risk ceiling of 34.
Each axis is a category. The shape matters more than the average — a healthy subject fills the whole shape, while a spike-and-crater profile means strength in one dimension is masking risk in another.
The weighted overall 73 is calibrated to 87 on the published index scale (record calibration 2026-08-02).
This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.
| Registry | Package | Version | Downloads / mo | Versions | Last publish | Tags |
|---|---|---|---|---|---|---|
| Packagist | squizlabs/php_codesniffer | 4.0.4 | 7,942,607 | 109 | 21 days ago | static-analysisstandardsphpcs |
Is the project alive — is code being written and are releases shipping?
| 36/36 | Push recency — last push 5 days ago |
| 29.1/36 | Commit cadence — 42/52 weeks with commits |
| 18/18 | Commit volume — 433 commits in the last year |
| 10/10 | OpenSSF Scorecard: Maintained — 30 commit(s) and 7 issue activity found in the last 90 days -- score normalized to 10 |
| commits_last_year | 433 |
| human_commit_share | 0.85 |
| days_since_last_push | 5 |
| active_weeks_last_year | 42 |
| 27/27 | Ships releases — 85 releases published |
| 36/36 | Release recency — latest release 21 days ago |
| 19.8/27 | Release cadence — a release every ~46 days |
| 8/10 | OpenSSF Scorecard: Signed-Releases — 4 out of the last 4 releases have a total of 4 signed artifacts. |
| releases_count | 85 |
| latest_release_tag | 4.0.4 |
| releases_from_tags | no |
| days_since_latest_release | 21 |
| mean_days_between_releases | 46 |
Does the project have users, downloads, attention, and a welcoming setup for contributors?
| 51.8/60 | Stars — 1,551 stars |
| 17.1/25 | Forks — 115 forks |
| 6.5/15 | Watchers — 16 watchers |
| forks | 115 |
| stars | 1,551 |
| watchers | 16 |
| growth_state | unverified |
| growth_factor_pct | 100 |
| growth_unverified_reason | no_history |
| 22.5/22.5 | README |
| 22.5/22.5 | License — recognized license (BSD-3-Clause) |
| 18/18 | CONTRIBUTING guide |
| 13.5/13.5 | Code of conduct |
| 0/7.2 | Issue template |
| 6.3/6.3 | PR template |
| has_readme | yes |
| has_license | yes |
| readme_badges | 7 |
| has_contributing | yes |
| has_issue_template | no |
| has_code_of_conduct | yes |
| readme_badge_services | coveralls.io, github.com, shields.io |
| has_pull_request_template | yes |
| 80/80 | Monthly downloads — 7,942,607 downloads/month across packagist |
| 20/20 | Registry dependents — 29,286 packages depend on it |
| packages | squizlabs/php_codesniffer |
| dependents | 29,286 |
| ecosystems | packagist |
| total_downloads | 399,167,819 |
| monthly_downloads | 7,942,607 |
| unverified_packages_excluded | — |
Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?
| 9/54 | Bus factor — 1 contributor(s) cover half of all commits |
| 9.4/22.5 | Commit distribution — top contributor authored 58% of commits |
| 13.5/13.5 | Contributor breadth — 98 contributors |
| 10/10 | OpenSSF Scorecard: Contributors — project has 72 contributing companies or organizations |
| bus_factor | 1 |
| contributors_sampled | 98 |
| top_contributor_share | 0.582 |
| 21.5/42 | Issue resolution — 51% of issues closed |
| 28.2/30 | PR acceptance — 992/1,054 decided PRs merged |
| 10.4/13 | Newcomer PR acceptance — 4/5 first-time contributors' PRs merged in 30d |
| 0/15 | OpenSSF Scorecard: Code-Review — Found 1/22 approved changesets -- score normalized to 0 |
| merged_prs | 992 |
| open_issues | 166 |
| closed_issues | 174 |
| prs_merged_7d | 1 |
| prs_decided_7d | 1 |
| prs_merged_30d | 18 |
| prs_decided_30d | 19 |
| issue_closed_ratio | 0.512 |
| closed_unmerged_prs | 62 |
| first_time_authors_30d | 4 |
| first_time_prs_merged_30d | 4 |
| first_time_prs_decided_30d | 5 |
| 30/30 | Ownership backing — organization-owned |
| 0/20 | Verified domain |
| 13.9/25 | Owner reach — 86 followers of PHPCSStandards |
| 19.9/25 | Track record — 11 public repos, account ~7 yr old |
| followers | 86 |
| owner_type | Organization |
| is_verified | no |
| owner_login | PHPCSStandards |
| public_repos | 11 |
| account_age_days | 2,572 |
| 25/25 | Published & resolvable — 1 package(s) on packagist |
| 35/35 | Publish recency — latest publish 21 days ago |
| 20/20 | Version history — 109 published versions |
| 20/20 | Not deprecated — active, not deprecated or yanked |
| packages | squizlabs/php_codesniffer |
| ecosystems | packagist |
| any_deprecated | no |
| min_days_since_publish | 21 |
Are baseline engineering and documentation practices in place?
| 24/24 | CI workflows — 14 workflow(s) |
| 24/24 | Tests present |
| 0/16 | Linter config |
| 0/9.6 | Pre-commit hooks |
| 0/6.4 | .editorconfig |
| 20/20 | OpenSSF Scorecard: CI-Tests — 9 out of 9 merged PRs checked by a CI test -- score normalized to 10 |
| has_ci | yes |
| has_tests | yes |
| has_editorconfig | no |
| has_linter_config | no |
| has_precommit_config | no |
| 30/30 | README |
| 0/25 | Documentation directory |
| 0/15 | Documentation / homepage site |
| 10/10 | Repository description |
| 10/10 | Topics — 11 topics |
| 10/10 | Wiki |
| topics | automation, cli, coding-standards, php, phpcbf, phpcs, psr1, psr12, psr2, qa, static-analysis |
| has_wiki | yes |
| homepage | — |
| docs_site | — |
| has_readme | yes |
| has_docs_dir | no |
| has_description | yes |
Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?
| 7.5/7.5 | Binary-Artifacts — no binaries found in the repo |
| 0/7.5 | Branch-Protection — no data |
| 2.5/2.5 | CI-Tests — 9 out of 9 merged PRs checked by a CI test -- score normalized to 10 |
| 0/2.5 | CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected |
| 0/7.5 | Code-Review — Found 1/22 approved changesets -- score normalized to 0 |
| 2.5/2.5 | Contributors — project has 72 contributing companies or organizations |
| 0/10 | Dangerous-Workflow — no data |
| 7.5/7.5 | Dependency-Update-Tool — update tool detected |
| 0/5 | Fuzzing — project is not fuzzed |
| 2.5/2.5 | License — license file detected |
| 7.5/7.5 | Maintained — 30 commit(s) and 7 issue activity found in the last 90 days -- score normalized to 10 |
| 0/5 | Packaging — no data |
| 0/5 | Pinned-Dependencies — no data |
| 0/5 | SAST — SAST tool is not run on all commits -- score normalized to 0 |
| 2/5 | Security-Policy — security policy file detected |
| 6/7.5 | Signed-Releases — 4 out of the last 4 releases have a total of 4 signed artifacts. |
| 0/7.5 | Token-Permissions — no data |
| 7.5/7.5 | Vulnerabilities — 0 existing vulnerabilities detected |
| source | openssf_scorecard |
| checks_evaluated | 13 |
| scorecard_version | v5.5.0 |
| checks_inconclusive | 5 |
| scorecard_aggregate | 6.5 |
How well is the repo equipped to be developed and maintained with AI coding agents? Carries a deliberately small weight (4%): agent tooling is a real maintenance signal, but a repository with none can still reach 100/100.
| 0/45 | Agent instructions — no CLAUDE.md / AGENTS.md / editor rules |
| 0/15 | Machine-readable docs (llms.txt) |
| 31.4/40 | Legible commit history — 50 of 85 human commits state their intent (structured subject or explanatory body) |
| has_llms_txt | no |
| llms_txt_url | — |
| legible_history_share | 0.588 |
| agent_instruction_files | — |
| agent_instruction_max_bytes | — |
| 0/18 | One-command bootstrap |
| 22/22 | Automated tests |
| 0/11 | Lint / format config |
| 0/11 | Static type checking |
| 0/10 | Reproducible environment |
| 0/10 | Demonstrated agent practice — no agent-authored commits among the last 100 |
| 8/8 | Automated maintenance — 15 of the last 100 commits are automated dependency updates |
| 0/10 | OpenSSF Scorecard: Pinned-Dependencies — no data |
| has_nix | no |
| has_tests | yes |
| lockfiles | — |
| has_dockerfile | no |
| typed_language | no |
| bootstrap_files | — |
| has_devcontainer | no |
| has_linter_config | no |
| typecheck_configs | — |
| agent_commit_share | 0 |
| toolchain_manifests | — |
| dependency_bot_commit_share | 0.15 |
| 0/45 | Type-checkable code — PHP without a type-check config |
| 54.4/55 | Manageable file sizes — 8/785 source files over 60KB |
| primary_language | PHP |
| largest_source_bytes | 178,514 |
| source_files_sampled | 785 |
| oversized_source_files | 8 |
When each star and fork was added, collected from GitHub and bucketed by day. Cumulative growth sits directly above the daily additions it is made of, so the two read against each other: steady organic accretion looks nothing like an abrupt, short-lived burst. Where that difference is measurable, it is reported as growth authenticity.
Each point covers 5 days.
Independent, tool-agnostic security assessment from the open-source OpenSSF Scorecard. Each check rewards a security practice, not a specific vendor's tool. Checks Scorecard could not determine are marked n/a and excluded from the security score (never counted as zero).
| 10 | Binary-Artifacts | no binaries found in the repo |
| n/a | Branch-Protection | internal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md |
| 10 | CI-Tests | 9 out of 9 merged PRs checked by a CI test -- score normalized to 10 |
| 0 | CII-Best-Practices | no effort to earn an OpenSSF best practices badge detected |
| 0 | Code-Review | Found 1/22 approved changesets -- score normalized to 0 |
| 10 | Contributors | project has 72 contributing companies or organizations |
| n/a | Dangerous-Workflow | no workflows found |
| 10 | Dependency-Update-Tool | update tool detected |
| 0 | Fuzzing | project is not fuzzed |
| 10 | License | license file detected |
| 10 | Maintained | 30 commit(s) and 7 issue activity found in the last 90 days -- score normalized to 10 |
| n/a | Packaging | packaging workflow not detected |
| n/a | Pinned-Dependencies | no dependencies found |
| 0 | SAST | SAST tool is not run on all commits -- score normalized to 0 |
| 4 | Security-Policy | security policy file detected |
| 8 | Signed-Releases | 4 out of the last 4 releases have a total of 4 signed artifacts. |
| n/a | Token-Permissions | No tokens found |
| 10 | Vulnerabilities | 0 existing vulnerabilities detected |
Full resolved dependency set from the GitHub dependency graph: 0 direct and 6 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.
| Registry | Package | Version | Relation |
|---|---|---|---|
| Packagist | ext-libxml | — | indirect |
| Packagist | ext-simplexml | — | indirect |
| Packagist | ext-tokenizer | — | indirect |
| Packagist | ext-xmlwriter | — | indirect |
| Packagist | php | — | indirect |
| Packagist | phpunit/phpunit | — | indirect |
Advisory matching could not run for this report: No resolved dependencies carried a version and a supported ecosystem
Spotted something off in this report, or have thoughts to share? Wrong measurements, missed tooling, ideas, questions — anything is welcome. Every message is read and gets a response.
Scores are signals, not warranties. They reflect publicly visible practices on GitHub — not a code audit, and not a security guarantee.
Missing data is excluded and weights renormalized, never scored as zero. Methodology is versioned and open: metrics v2.10.0, schema v0.34.0 — full methodology · metrics wiki.
How one result sits in the wider record: aggregate statistics — Packagist.