Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-20 04:50 UTC

phpstan / phpdoc-parser

Next-gen phpDoc parser with support for intersection types and generics

PHPMIT★ 1,537 stars⑂ 78 forkssince Nov 2017View on GitHub ↗

phpstan/phpdoc-parser holds a health index of 93 out of 100, placing it in the Exceptional band. It scores highest on Engineering Quality (88/100) and lowest on AI Readiness (71/100). It was last updated 2 days ago. A single contributor accounts for most of its recent work.

93
overall / 100
Exceptional

Software health index

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.

93
Exceptional93-100The record's top tier (≈ top 5%); essentially all checked criteria met
Excellent80-92Strong across the board; minor gaps
Good65-79Healthy; gaps are limited and manageable
Moderate50-64Acceptable with notable gaps; review recommended
Weak35-49Material weaknesses across several areas
At Risk20-34Significant weaknesses; adoption warrants caution
Critical1-19Severe problems (abandoned, single-maintainer, no hygiene)
VitalityCommunity &AdoptionSustainability &GovernanceEngineeringQualitySecurityAI Readiness

Score profile

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 79 is calibrated to 93 on the published index scale (record calibration 2026-08-02).

Ownership

PHPStanOrganization · verified domain
260 followers25 public repossince Dec 2015

This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Packagistphpstan/phpdoc-parser2.3.618,325,94311222 days ago

Metrics by category

Vitality

Is the project alive — is code being written and are releases shipping?

80Excellent · 21% of overall
How it's scored
36/36Push recency — last push 2 days ago
11.8/36Commit cadence — 17/52 weeks with commits
14.7/18Commit volume — 42 commits in the last year
10/10OpenSSF Scorecard: Maintained — 13 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year42
human_commit_share0.88
days_since_last_push2
active_weeks_last_year17
How it's scored
27/27Ships releases — 100 releases published
36/36Release recency — latest release 22 days ago
19.8/27Release cadence — a release every ~65.2 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count100
latest_release_tag2.3.6
releases_from_tagsno
days_since_latest_release22
mean_days_between_releases65.2
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Signed-Releases. Remaining weights renormalized.

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

76Good · 17% of overall
How it's scored
51.7/60Stars — 1,537 stars
15.7/25Forks — 78 forks
3.9/15Watchers — 6 watchers
Inputs used
forks78
stars1,537
watchers6
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
0/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges4
has_contributingno
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesgithub.com, poser.pugx.org, shields.io
has_pull_request_templateno
How it's scored
80/80Monthly downloads — 18,325,943 downloads/month across packagist
18.6/20Registry dependents — 607 packages depend on it
Inputs used
packagesphpstan/phpdoc-parser
dependents607
ecosystemspackagist
total_downloads419,722,377
monthly_downloads18,325,943
unverified_packages_excluded—

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

75Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
10.4/22.5Commit distribution — top contributor authored 54% of commits
13.5/13.5Contributor breadth — 49 contributors
10/10OpenSSF Scorecard: Contributors — project has 21 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled49
top_contributor_share0.537
How it's scored
38.3/42Issue resolution — 91% of issues closed
24/30PR acceptance — 172/215 decided PRs merged
13/13Newcomer PR acceptance — 1/1 first-time contributors' PRs merged in 30d
3/15OpenSSF Scorecard: Code-Review — Found 4/18 approved changesets -- score normalized to 2
Inputs used
merged_prs172
open_issues8
closed_issues83
prs_merged_7d0
prs_decided_7d0
prs_merged_30d1
prs_decided_30d1
issue_closed_ratio0.912
closed_unmerged_prs43
first_time_authors_30d1
first_time_prs_merged_30d1
first_time_prs_decided_30d1
How it's scored
30/30Ownership backing — organization-owned
20/20Verified domain
17.4/25Owner reach — 260 followers of phpstan
22.3/25Track record — 25 public repos, account ~10 yr old
Inputs used
followers260
owner_typeOrganization
is_verifiedyes
owner_loginphpstan
public_repos25
account_age_days3,951

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on packagist
35/35Publish recency — latest publish 22 days ago
20/20Version history — 112 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesphpstan/phpdoc-parser
ecosystemspackagist
any_deprecatedno
min_days_since_publish22

Engineering Quality

Are baseline engineering and documentation practices in place?

88Excellent · 19% of overall
How it's scored
24/24CI workflows — 12 workflow(s)
24/24Tests present
16/16Linter config — phpcs.xml, phpstan.neon
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 19 out of 19 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configno

Documentation

85Excellent
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics — 8 topics
10/10Wiki
Inputs used
topicsphpstan, static-analysis, php, php7, testing, static-code-analysis, static-analyzer, phpdoc
has_wikiyes
homepage—
docs_site—
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?

78Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
2.2/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2.5/2.5CI-Tests — 19 out of 19 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
1.5/7.5Code-Review — Found 4/18 approved changesets -- score normalized to 2
2.5/2.5Contributors — project has 21 contributing companies or organizations
0/10Dangerous-Workflow — no data
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 13 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
0/5Pinned-Dependencies — no data
4.5/5SAST — SAST tool is not run on all commits -- score normalized to 9
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — no data
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate7.2
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories15
affected_packages1
assessed_packages34
unassessed_packages12
affected_by_severityhigh 1
direct_affected_packages0
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 34 resolved dependencies against OSV. 12 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list. This repository publishes no package the index resolves, so the repository dependency graph was assessed instead. That graph mixes development and test pins with shipped dependencies, so only the declared runtime dependencies are scored; transitive findings are reported as context and excluded from the score. Reachability is not analyzed.

AI Readiness

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.

71Good · 4% of overall
How it's scored
45/45Agent instructions — CLAUDE.md
0/15Machine-readable docs (llms.txt)
10.9/40Legible commit history — 18 of 88 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.205
agent_instruction_filesCLAUDE.md
agent_instruction_max_bytes8,477
How it's scored
18/18One-command bootstrap — Makefile
22/22Automated tests
11/11Lint / format config — phpcs.xml, phpstan.neon
0/11Static type checking
10/10Reproducible environment — lockfile
10/10Demonstrated agent practice — 12 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 12 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsyes
lockfilescomposer.lock
has_dockerfileno
typed_languageno
bootstrap_filesMakefile
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0.12
toolchain_manifests—
dependency_bot_commit_share0.12
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
0/45Type-checkable code — PHP without a type-check config
53.7/55Manageable file sizes — 3/123 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes199,834
source_files_sampled123
oversized_source_files3

Key facts

1,537GitHub stars
49contributors
42commits, last 12 months
2days since last push
100releases
1bus factor
8open issues
Packagistpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

Star and fork history 0 ★ / 78 ⇿
0Stars
78Forks
99Releases

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.

0204060807832017-112022-042026-09
Major 2Minor 37Patch 60

Each point covers 9 days.

OpenSSF Scorecard 7.2 / 10
7.2aggregate

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).Scorecard v5.5.0 · 2026-10-20 04:50 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests19 out of 19 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
2Code-ReviewFound 4/18 approved changesets -- score normalized to 2
10Contributorsproject has 21 contributing companies or organizations
n/aDangerous-Workflowno workflows found
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained13 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
9SASTSAST tool is not run on all commits -- score normalized to 9
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 1
RegistryPackageVersion constraintManifest
Packagistapigen/apigen^7.0.0apigen/composer.json
All dependencies 46

Full resolved dependency set from the GitHub dependency graph: 1 direct and 45 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.

RegistryPackageVersionRelation
Packagistapigen/apigen—direct
Packagistdflydev/dot-access-data 3-dev.0indirect
Packagistdoctrine/annotations—indirect
Packagistjetbrains/phpstorm-stubs2022.3indirect
Packagistlaminas/laminas-code4.17.0indirect
Packagistlatte/latte3.0-devindirect
Packagistleague/commonmark2.5-devindirect
Packagistleague/config1.2-devindirect
Packagistnette/di 3.2-dev.0indirect
Packagistnette/finder3.0-devindirect
Packagistnette/neon3.4-devindirect
Packagistnette/php-generator4.0-devindirect
Packagistnette/robot-loader4.0-devindirect
Packagistnette/schema 1.2-dev.0indirect
Packagistnette/utils4.0-devindirect
Packagistnikic/php-parser—indirect
Packagistnikic/php-parser 4-dev.0indirect
Packagistphp—indirect
Packagistphp-parallel-lint/php-parallel-lint—indirect
Packagistphplrt/phplrt—indirect
Packagistphpstan/extension-installer—indirect
Packagistphpstan/php-8-stubs0.3.60indirect
Packagistphpstan/phpdoc-parser 1.21-dev.0indirect
Packagistphpstan/phpstan—indirect
Packagistphpstan/phpstan-phpunit—indirect
Packagistphpstan/phpstan-strict-rules—indirect
Packagistphpunit/phpunit—indirect
Packagistpsr/container 2.0-dev.0indirect
Packagistpsr/container2.0.2indirect
Packagistpsr/event-dispatcher 1.0-dev.0indirect
Packagistsymfony/console 6.3-dev.0indirect
Packagistsymfony/console8.0.15indirect
Packagistsymfony/deprecation-contracts3.3-devindirect
Packagistsymfony/deprecation-contracts3.7.1indirect
Packagistsymfony/polyfill-ctype1.37.0indirect
Packagistsymfony/polyfill-intl-grapheme1.28-devindirect
Packagistsymfony/polyfill-intl-grapheme1.41.0indirect
Packagistsymfony/polyfill-intl-normalizer1.28-devindirect
Packagistsymfony/polyfill-intl-normalizer1.42.0indirect
Packagistsymfony/polyfill-mbstring1.38.2indirect
Packagistsymfony/process—indirect
Packagistsymfony/service-contracts3.3-devindirect
Packagistsymfony/service-contracts3.7.1indirect
Packagistsymfony/string 6.3-dev.0indirect
Packagistsymfony/string8.0.15indirect
Packagisttwig/twig3.28.0indirect
Dependency advisories 1

This repository publishes no package the index resolves, so its own dependency graph was assessed — 34 packages, which also include development and test pins that never ship: 1 carry known advisories, of which 0 are direct. 12 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.

PackageVersionRelationSeverityAdvisoriesFixed in
league/commonmark2.5-devindirecthigh152.10.2

An advisory means the version recorded in the dependency graph falls inside an advisory’s affected range. Reachability is not analysed, and the graph includes development and test pins — a finding may concern tooling rather than shipped software.

Raw JSON report machine-readable

Feedback

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.

The message is kept through sign-in.

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.