Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-27 20:57 UTC

phpstan / phpstan-doctrine

Doctrine extensions for PHPStan

PHPMIT★ 675 stars⑂ 121 forkssince Jan 2017View on GitHub ↗

phpstan/phpstan-doctrine holds a health index of 92 out of 100, placing it in the Excellent band. It scores highest on Vitality (92/100) and lowest on Community & Adoption (70/100). It was last updated today. A single contributor accounts for most of its recent work.

92
overall / 100
Excellent

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.

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

Ownership

PHPStanOrganization · verified domain
254 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 publishTags
Packagistphpstan/phpstan-doctrine2.0.282,171,36519445 days agostatic-analysis

Metrics by category

Vitality

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

92Excellent · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
22.8/36Commit cadence33/52 weeks with commits
16.9/18Commit volume76 commits in the last year
10/10OpenSSF Scorecard: Maintained20 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year76
human_commit_share0.87
days_since_last_push0
active_weeks_last_year33

Release discipline

100Exceptional
How it's scored
27/27Ships releases100 releases published
36/36Release recencylatest release 45 days ago
27/27Release cadencea release every ~13.9 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count100
latest_release_tag2.0.28
releases_from_tagsno
days_since_latest_release45
mean_days_between_releases13.9
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?

70Good · 17% of overall
How it's scored
45.9/60Stars675 stars
17.3/25Forks121 forks
4.7/15Watchers8 watchers
Inputs used
forks121
stars675
watchers8
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges3
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com, poser.pugx.org
has_pull_request_templateno
How it's scored
80/80Monthly downloads2,171,365 downloads/month across packagist
20/20Registry dependents1,177 packages depend on it
Inputs used
packagesphpstan/phpstan-doctrine
dependents1,177
ecosystemspackagist
total_downloads76,949,044
monthly_downloads2,171,365
unverified_packages_excluded

Sustainability & Governance

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

74Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
8.6/22.5Commit distributiontop contributor authored 62% of commits
13.5/13.5Contributor breadth79 contributors
10/10OpenSSF Scorecard: Contributorsproject has 35 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled79
top_contributor_share0.616
How it's scored
32.8/42Issue resolution78% of issues closed
23/30PR acceptance314/409 decided PRs merged
13/13Newcomer PR acceptance1/1 first-time contributors' PRs merged in 30d
6/15OpenSSF Scorecard: Code-ReviewFound 10/21 approved changesets -- score normalized to 4
Inputs used
merged_prs314
open_issues78
closed_issues280
prs_merged_7d1
prs_decided_7d1
prs_merged_30d2
prs_decided_30d2
issue_closed_ratio0.782
closed_unmerged_prs95
first_time_authors_30d1
first_time_prs_merged_30d1
first_time_prs_decided_30d1
How it's scored
30/30Ownership backingorganization-owned
20/20Verified domain
17.3/25Owner reach254 followers of phpstan
22.3/25Track record25 public repos, account ~10 yr old
Inputs used
followers254
owner_typeOrganization
is_verifiedyes
owner_loginphpstan
public_repos25
account_age_days3,898

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on packagist
35/35Publish recencylatest publish 45 days ago
20/20Version history194 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesphpstan/phpstan-doctrine
ecosystemspackagist
any_deprecatedno
min_days_since_publish45

Engineering Quality

Are baseline engineering and documentation practices in place?

78Good · 19% of overall
How it's scored
24/24CI workflows9 workflow(s)
24/24Tests present
16/16Linter configphpstan.neon
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests24 out of 24 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

60Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics9 topics
10/10Wiki
Inputs used
topicsphp, php7, phpstan, static-analysis, testing, static-code-analysis, static-analyzer, doctrine, doctrine2
has_wikiyes
homepage
docs_site
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

75Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
2.2/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
2.5/2.5CI-Tests24 out of 24 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
3/7.5Code-ReviewFound 10/21 approved changesets -- score normalized to 4
2.5/2.5Contributorsproject has 35 contributing companies or organizations
0/10Dangerous-Workflowno data
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained20 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
0/5Pinned-Dependenciesno data
5/5SASTSAST tool is run on all commits
5/5Security-Policysecurity policy file detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsno data
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate7.5
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. Remaining weights renormalized.

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.

76Good · 4% of overall
How it's scored
45/45Agent instructionsCLAUDE.md
0/15Machine-readable docs (llms.txt)
24.5/40Legible commit history40 of 87 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.46
agent_instruction_filesCLAUDE.md
agent_instruction_max_bytes8,858
How it's scored
18/18One-command bootstrapMakefile
22/22Automated tests
11/11Lint / format configphpstan.neon
0/11Static type checking
10/10Reproducible environmentDockerfile
10/10Demonstrated agent practice10 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance13 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileyes
typed_languageno
bootstrap_filesMakefile
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share0.1
toolchain_manifests
dependency_bot_commit_share0.13
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
0/45Type-checkable codePHP without a type-check config
54.6/55Manageable file sizes2/294 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes181,220
source_files_sampled294
oversized_source_files2

Key facts

675GitHub stars
79contributors
76commits, last 12 months
0days since last push
100releases
1bus factor
78open issues
Packagistpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • No resolved dependencies carried a version and a supported ecosystem

More detail

Star and fork history 0 ★ / 121 ⇿
0Stars
121Forks
100Releases

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.

025507510012512132017-032021-112026-08
Major 1Minor 2Patch 97

Each point covers 9 days.

OpenSSF Scorecard 7.5 / 10
7.5aggregate

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-08-27 20:57 UTC

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

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

RegistryPackageVersionRelation
Packagistcache/array-adapterindirect
Packagistcomposer/semverindirect
Packagistcweagans/composer-patchesindirect
Packagistdoctrine/annotationsindirect
Packagistdoctrine/collectionsindirect
Packagistdoctrine/commonindirect
Packagistdoctrine/dbalindirect
Packagistdoctrine/lexerindirect
Packagistdoctrine/mongodb-odmindirect
Packagistdoctrine/ormindirect
Packagistdoctrine/persistenceindirect
Packagistgedmo/doctrine-extensionsindirect
Packagistnesbot/carbonindirect
Packagistphpindirect
Packagistphp-parallel-lint/php-parallel-lintindirect
Packagistphpstan/phpstanindirect
Packagistphpstan/phpstan-deprecation-rulesindirect
Packagistphpstan/phpstan-phpunitindirect
Packagistphpstan/phpstan-strict-rulesindirect
Packagistphpunit/phpunitindirect
Packagistramsey/uuidindirect
Packagistshipmonk/name-collision-detectorindirect
Packagistsymfony/cacheindirect
Packagistsymfony/uidindirect
Dependency advisories not assessed

Advisory matching could not run for this report: No resolved dependencies carried a version and a supported ecosystem

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 statisticsPackagist.