Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-12 00:38 UTC

mglaman / phpstan-drupal

Extension for PHPStan to allow analysis of Drupal code.

PHPMIT★ 208 stars⑂ 86 forkssince Dec 2018View on GitHub ↗

mglaman/phpstan-drupal holds a health index of 86 out of 100, placing it in the Excellent band. It scores highest on Vitality (86/100) and lowest on Security (57/100). It was last updated 2 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

Matt GlamanPersonal account
380 followers279 public repossince Feb 2013@acquia

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Packagistmglaman/phpstan-drupal2.2.0871,8091202 days ago

Metrics by category

Vitality

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

86Excellent · 21% of overall
How it's scored
36/36Push recency — last push 2 days ago
13.2/36Commit cadence — 19/52 weeks with commits
17.1/18Commit volume — 79 commits in the last year
10/10OpenSSF Scorecard: Maintained — 27 commit(s) and 10 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year79
human_commit_share0.93
days_since_last_push2
active_weeks_last_year19

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 100 releases published
36/36Release recency — latest release 2 days ago
27/27Release cadence — a release every ~17.2 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count100
latest_release_tag2.2.0
releases_from_tagsno
days_since_latest_release2
mean_days_between_releases17.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?

69Good · 17% of overall
How it's scored
37.6/60Stars — 208 stars
16.1/25Forks — 86 forks
3.3/15Watchers — 5 watchers
Inputs used
forks86
stars208
watchers5
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_badges2
has_contributingno
has_issue_templateno
has_code_of_conductyes
readme_badge_servicescircleci.com, github.com
has_pull_request_templateno
How it's scored
79.2/80Monthly downloads — 871,809 downloads/month across packagist
14.2/20Registry dependents — 134 packages depend on it
Inputs used
packagesmglaman/phpstan-drupal
dependents134
ecosystemspackagist
total_downloads33,459,051
monthly_downloads871,809
unverified_packages_excluded—

Sustainability & Governance

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

66Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
5.3/22.5Commit distribution — top contributor authored 77% of commits
13.5/13.5Contributor breadth — 60 contributors
10/10OpenSSF Scorecard: Contributors — project has 16 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled60
top_contributor_share0.766
How it's scored
32.6/42Issue resolution — 78% of issues closed
24.1/30PR acceptance — 432/538 decided PRs merged
13/13Newcomer PR acceptance — 1/1 first-time contributors' PRs merged in 30d
1.5/15OpenSSF Scorecard: Code-Review — Found 5/28 approved changesets -- score normalized to 1
Inputs used
merged_prs432
open_issues93
closed_issues321
prs_merged_7d10
prs_decided_7d11
prs_merged_30d11
prs_decided_30d12
issue_closed_ratio0.775
closed_unmerged_prs106
first_time_authors_30d1
first_time_prs_merged_30d1
first_time_prs_decided_30d1
How it's scored
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
18.6/25Owner reach — 380 followers of mglaman
25/25Track record — 279 public repos, account ~13 yr old
Inputs used
followers380
owner_typeUser
is_verified—
owner_loginmglaman
public_repos279
account_age_days4,946
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on packagist
35/35Publish recency — latest publish 2 days ago
20/20Version history — 120 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesmglaman/phpstan-drupal
ecosystemspackagist
any_deprecatedno
min_days_since_publish2

Engineering Quality

Are baseline engineering and documentation practices in place?

79Good · 19% of overall
How it's scored
24/24CI workflows — 3 workflow(s)
24/24Tests present
16/16Linter config — phpcs.xml, phpstan.neon
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
18/20OpenSSF Scorecard: CI-Tests — 29 out of 30 merged PRs checked by a CI test -- score normalized to 9
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://phpstan-drupal.mglaman.dev/
10/10Repository description
10/10Topics — 5 topics
0/10Wiki
Inputs used
topicsphpstan, drupal, static-analysis, php, hacktoberfest
has_wikino
homepagehttps://phpstan-drupal.mglaman.dev/
docs_sitehttps://phpstan-drupal.mglaman.dev/
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

57Moderate · 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.2/2.5CI-Tests — 29 out of 30 merged PRs checked by a CI test -- score normalized to 9
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0.8/7.5Code-Review — Found 5/28 approved changesets -- score normalized to 1
2.5/2.5Contributors — project has 16 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 — 27 commit(s) and 10 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
0/5Pinned-Dependencies — no data
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
0/5Security-Policy — security policy file not 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_aggregate5.8
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.

72Good · 4% of overall
How it's scored
45/45Agent instructions — .github/copilot-instructions.md, CLAUDE.md
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://phpstan-drupal.mglaman.dev/llms.txt)
40/40Legible commit history — 85 of 93 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://phpstan-drupal.mglaman.dev/llms.txt
legible_history_share0.914
agent_instruction_files.github/copilot-instructions.md, CLAUDE.md
agent_instruction_max_bytes1,643
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — phpcs.xml, phpstan.neon
0/11Static type checking
0/10Reproducible environment
10/10Demonstrated agent practice — 48 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 7 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0.48
toolchain_manifests—
dependency_bot_commit_share0.07
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
55/55Manageable file sizes — 0/319 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes18,845
source_files_sampled319
oversized_source_files0

Key facts

208GitHub stars
60contributors
79commits, last 12 months
2days since last push
100releases
1bus factor
93open 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 ★ / 86 ⇿
0Stars
86Forks
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.

0204060801008642019-012022-112026-08
Major 2Minor 4Patch 93

Each point covers 7 days.

OpenSSF Scorecard 5.8 / 10
5.8aggregate

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-09-12 00:38 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
9CI-Tests29 out of 30 merged PRs checked by a CI test -- score normalized to 9
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1Code-ReviewFound 5/28 approved changesets -- score normalized to 1
10Contributorsproject has 16 contributing companies or organizations
n/aDangerous-Workflowno workflows found
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained27 commit(s) and 10 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 3
RegistryPackageVersion constraintManifest
Packagistsymfony/finder^6.2 || ^7.0 || ^8.0composer.json
Packagistsymfony/yaml^6.2 || ^7.0 || ^8.0composer.json
Packagistwebflo/drupal-finder^1.3.1 || ^2.0composer.json
All dependencies 16

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

RegistryPackageVersionRelation
Packagistsymfony/finder—direct
Packagistsymfony/yaml—direct
Packagistwebflo/drupal-finder—direct
Packagistbehat/mink—indirect
Packagistcomposer/installers—indirect
Packagistdrupal/core-recommended—indirect
Packagistdrush/drush—indirect
Packagistphp—indirect
Packagistphpstan/extension-installer—indirect
Packagistphpstan/phpstan—indirect
Packagistphpstan/phpstan-deprecation-rules—indirect
Packagistphpstan/phpstan-strict-rules—indirect
Packagistphpunit/phpunit—indirect
Packagistslevomat/coding-standard—indirect
Packagistsquizlabs/php_codesniffer—indirect
Packagistsymfony/phpunit-bridge—indirect
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 statistics — Packagist.