Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-15 02:34 UTC

ashhitch / wp-graphql-yoast-seo

This is an extension to the WPGraphQL plugin for Yoast SEO

PHPGPL-3.0★ 231 stars⑂ 49 forkssince Jan 2019View on GitHub ↗
KindPluginNetwork serviceLibraryhow this is determined

ashhitch/wp-graphql-yoast-seo holds a health index of 56 out of 100, placing it in the Moderate band. It scores highest on Sustainability & Governance (60/100) and lowest on Security (50/100). It was last updated 34 days ago. A single contributor accounts for most of its recent work.

56
overall / 100
Moderate

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.

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

Ownership

Ash HitchcockPersonal account
44 followers134 public repossince Sep 2012

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
Packagistashhitch/wp-graphql-yoast-seov5.1.04,9466334 days ago

Metrics by category

Vitality

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

52Moderate · 21% of overall
How it's scored
18/36Push recencylast push 34 days ago
4.8/36Commit cadence7/52 weeks with commits
10.3/18Commit volume13 commits in the last year
3/10OpenSSF Scorecard: Maintained4 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 3
Inputs used
commits_last_year13
human_commit_share0.91
days_since_last_push34
active_weeks_last_year7
How it's scored
27/27Ships releases65 releases published
36/36Release recencylatest release 34 days ago
12.6/27Release cadencea release every ~130 days
0/10OpenSSF Scorecard: Signed-ReleasesProject has not signed or included provenance with any releases.
Inputs used
releases_count65
latest_release_tagv5.1.0
releases_from_tagsno
days_since_latest_release34
mean_days_between_releases130

Community & Adoption

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

53Moderate · 17% of overall
How it's scored
38.3/60Stars231 stars
14/25Forks49 forks
4.7/15Watchers8 watchers
Inputs used
forks49
stars231
watchers8
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (GPL-3.0)
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_servicesposer.pugx.org
has_pull_request_templateno
How it's scored
49.3/80Monthly downloads4,946 downloads/month across packagist
0/20Registry dependents0 packages depend on it
Inputs used
packagesashhitch/wp-graphql-yoast-seo
dependents0
ecosystemspackagist
total_downloads228,963
monthly_downloads4,946
unverified_packages_excluded

Sustainability & Governance

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

60Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
3.1/22.5Commit distributiontop contributor authored 86% of commits
13.5/13.5Contributor breadth23 contributors
0/10OpenSSF Scorecard: Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled23
top_contributor_share0.862
How it's scored
33.6/42Issue resolution80% of issues closed
26.1/30PR acceptance88/101 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 2/21 approved changesets -- score normalized to 0
Inputs used
merged_prs88
open_issues20
closed_issues80
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.8
closed_unmerged_prs13
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
11.9/25Owner reach44 followers of ashhitch
25/25Track record134 public repos, account ~13 yr old
Inputs used
followers44
owner_typeUser
is_verified
owner_loginashhitch
public_repos134
account_age_days5,100
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on packagist
35/35Publish recencylatest publish 34 days ago
20/20Version history63 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesashhitch/wp-graphql-yoast-seo
ecosystemspackagist
any_deprecatedno
min_days_since_publish34

Engineering Quality

Are baseline engineering and documentation practices in place?

52Moderate · 19% of overall
How it's scored
24/24CI workflows3 workflow(s)
0/24Tests present
16/16Linter configphpcs.xml
0/9.6Pre-commit hooks
0/6.4.editorconfig
6/20OpenSSF Scorecard: CI-Tests5 out of 16 merged PRs checked by a CI test -- score normalized to 3
Inputs used
has_ciyes
has_testsno
has_editorconfigno
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/10Topics5 topics
10/10Wiki
Inputs used
topicswpgraphql-plugin, yoast-seo, wordpress, wordpress-plugin, graphql
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?

50Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
0.8/2.5CI-Tests5 out of 16 merged PRs checked by a CI test -- score normalized to 3
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 2/21 approved changesets -- score normalized to 0
0/2.5Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
2.2/7.5Maintained4 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 3
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-ReleasesProject has not signed or included provenance with any releases.
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
6.8/7.5Vulnerabilities1 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate3.7
Excluded from scoring (no data or not applicable): Packaging. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
0/25Indirect dependencies free of known advisoriestransitive set not separable from development and test dependencies in this scope
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories1
affected_packages1
assessed_packages43
unassessed_packages0
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 43 resolved dependencies against OSV. 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.

54Moderate · 4% of overall
How it's scored
45/45Agent instructionsAGENTS.md
15/15Machine-readable docs (llms.txt)llms.txt served by the project website (https://docs.docker.com/llms.txt)
28.7/40Legible commit history49 of 91 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://docs.docker.com/llms.txt
legible_history_share0.538
agent_instruction_filesAGENTS.md
agent_instruction_max_bytes5,973
How it's scored
0/18One-command bootstrap
0/22Automated tests
11/11Lint / format configphpcs.xml
0/11Static type checking
10/10Reproducible environmentDockerfile, lockfile
4/10Demonstrated agent practice2 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance9 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsno
lockfilescomposer.lock, pnpm-lock.yaml
has_dockerfileyes
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share0.02
toolchain_manifests
dependency_bot_commit_share0.09
How it's scored
0/45Type-checkable codePHP without a type-check config
55/55Manageable file sizes0/11 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes20,093
source_files_sampled11
oversized_source_files0
How it's scored
40/40API schema (OpenAPI/GraphQL/proto)all.graphql
0/20MCP server
0/40Runnable examples
Inputs used
example_dirs
has_mcp_signalno
api_schema_filesall.graphql
interfaces_expected_ofnetwork-service

Key facts

231GitHub stars
23contributors
13commits, last 12 months
34days since last push
65releases
1bus factor
20open issues
npm, Packagistpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Could not fetch npm package 'wp-graphql-yoast-seo' from its registry

More detail

Star and fork history 0 ★ / 49 ⇿
0Stars
49Forks
62Releases

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.

010203040504822019-072023-012026-08
Major 2Minor 27Patch 31

Each point covers 7 days.

OpenSSF Scorecard 3.7 / 10
3.7aggregate

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-15 02:33 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
3CI-Tests5 out of 16 merged PRs checked by a CI test -- score normalized to 3
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 2/21 approved changesets -- score normalized to 0
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
3Maintained4 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 3
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
9Vulnerabilities1 existing vulnerabilities detected
All dependencies 43

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

RegistryPackageVersionRelation
npm@prettier/plugin-php0.25.0indirect
npmansi-escapes7.3.0indirect
npmansi-regex6.2.2indirect
npmansi-styles6.2.3indirect
npmcli-cursor5.0.0indirect
npmcli-truncate5.2.0indirect
npmcolorette2.0.20indirect
npmcommander14.0.3indirect
npmemoji-regex10.6.0indirect
npmenvironment1.1.0indirect
npmeventemitter35.0.4indirect
npmget-east-asian-width1.6.0indirect
npmhusky9.1.7indirect
npmis-fullwidth-code-point5.1.0indirect
npmlinguist-languages8.2.0indirect
npmlint-staged16.4.0indirect
npmlistr29.0.5indirect
npmlog-update6.1.0indirect
npmmimic-function5.0.1indirect
npmonetime7.0.0indirect
npmphp-parser3.7.0indirect
npmpicomatch4.0.5indirect
npmprettier3.9.6indirect
npmrestore-cursor5.1.0indirect
npmrfdc1.4.1indirect
npmsignal-exit4.1.0indirect
npmslice-ansi7.1.2indirect
npmslice-ansi8.0.0indirect
npmstring-argv0.3.2indirect
npmstring-width7.2.0indirect
npmstring-width8.2.2indirect
npmstrip-ansi7.2.0indirect
npmtinyexec1.2.4indirect
npmwrap-ansi9.0.2indirect
npmyaml2.9.0indirect
Packagistautomattic/vipwpcs2.3.3indirect
Packagistdealerdirect/phpcodesniffer-composer-installer0.7.2indirect
Packagistphpcompatibility/php-compatibility9.3.5indirect
Packagistphpcompatibility/phpcompatibility-paragonie1.3.2indirect
Packagistphpcompatibility/phpcompatibility-wp2.1.4indirect
Packagistsirbrillig/phpcs-variable-analysis2.11.9indirect
Packagistsquizlabs/php_codesniffer3.13.6indirect
Packagistwp-coding-standards/wpcs2.3.0indirect
Dependency advisories 1

This repository publishes no package the index resolves, so its own dependency graph was assessed — 43 packages, which also include development and test pins that never ship: 1 carry known advisories, of which 0 are direct.

PackageVersionRelationSeverityAdvisoriesFixed in
wp-coding-standards/wpcs2.3.0indirecthigh13.4.1

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