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

statamic / seo-pro

SEO Pro is the all-in-one SEO toolkit for Statamic: meta tags, Open Graph, structured data, sitemaps, redirects, 404 tracking, and reporting that grades your whole site. One addon. No template gymnastics.

PHPNo license detected★ 73 stars⑂ 48 forkssince Jun 2018View on GitHub ↗

statamic/seo-pro holds a health index of 83 out of 100, placing it in the Excellent band. It scores highest on Vitality (91/100) and lowest on Community & Adoption (43/100). It was last updated 1 day ago. 2 contributors account for most of its recent work.

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

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

Ownership

StatamicOrganization · verified domain
412 followers77 public repossince Apr 2012

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Packagiststatamic/seo-prov7.14.132,9421231 day ago

Metrics by category

Vitality

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

91Excellent · 21% of overall
How it's scored
36/36Push recency — last push 1 days ago
28.4/36Commit cadence — 41/52 weeks with commits
18/18Commit volume — 344 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 10 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year344
human_commit_share0.94
days_since_last_push1
active_weeks_last_year41
How it's scored
27/27Ships releases — 100 releases published
36/36Release recency — latest release 1 days ago
27/27Release cadence — a release every ~8.6 days
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count100
latest_release_tagv7.14.1
releases_from_tagsno
days_since_latest_release1
mean_days_between_releases8.6

Community & Adoption

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

43Weak · 17% of overall
How it's scored
30.1/60Stars — 73 stars
13.9/25Forks — 48 forks
4.7/15Watchers — 8 watchers
Inputs used
forks48
stars73
watchers8
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
0/22.5License — no license file detected
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseno
readme_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateno
How it's scored
60.2/80Monthly downloads — 32,942 downloads/month across packagist
0/20Registry dependents — 0 packages depend on it
Inputs used
packagesstatamic/seo-pro
dependents0
ecosystemspackagist
total_downloads590,608
monthly_downloads32,942
unverified_packages_excluded—

Sustainability & Governance

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

82Excellent · 23% of overall
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
15/22.5Commit distribution — top contributor authored 33% of commits
13.5/13.5Contributor breadth — 36 contributors
10/10OpenSSF Scorecard: Contributors — project has 14 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled36
top_contributor_share0.334
How it's scored
40.9/42Issue resolution — 97% of issues closed
25.9/30PR acceptance — 279/323 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
1.5/15OpenSSF Scorecard: Code-Review — Found 5/27 approved changesets -- score normalized to 1
Inputs used
merged_prs279
open_issues9
closed_issues320
prs_merged_7d8
prs_decided_7d9
prs_merged_30d10
prs_decided_30d11
issue_closed_ratio0.973
closed_unmerged_prs44
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
30/30Ownership backing — organization-owned
20/20Verified domain
18.8/25Owner reach — 412 followers of statamic
25/25Track record — 77 public repos, account ~14 yr old
Inputs used
followers412
owner_typeOrganization
is_verifiedyes
owner_loginstatamic
public_repos77
account_age_days5,251

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on packagist
35/35Publish recency — latest publish 1 days ago
20/20Version history — 123 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesstatamic/seo-pro
ecosystemspackagist
any_deprecatedno
min_days_since_publish1

Engineering Quality

Are baseline engineering and documentation practices in place?

67Good · 19% of overall
How it's scored
24/24CI workflows — 4 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 24 out of 24 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://statamic.com/addons/statamic/seo-pro
10/10Repository description
10/10Topics — 5 topics
0/10Wiki
Inputs used
topicsseo, statamic, addon, statamic-addon, search-optimization
has_wikino
homepagehttps://statamic.com/addons/statamic/seo-pro
docs_sitehttps://statamic.com/addons/statamic/seo-pro
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

59Moderate · 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 — 24 out of 24 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
0.8/7.5Code-Review — Found 5/27 approved changesets -- score normalized to 1
2.5/2.5Contributors — project has 14 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
0/2.5License — license file not detected
7.5/7.5Maintained — 30 commit(s) and 10 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
5/5Pinned-Dependencies — all dependencies are pinned
3.5/5SAST — SAST tool is not run on all commits -- score normalized to 7
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — Project has not signed or included provenance with any releases.
7.5/7.5Token-Permissions — GitHub workflow tokens follow principle of least privilege
1.5/7.5Vulnerabilities — 8 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate5.8
Excluded from scoring (no data or not applicable): Packaging. Remaining weights renormalized.
How it's scored
14/35Direct dependencies free of known advisories — 1 affected: underscore 1.12.1 (high 7.5)
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
33.7/40No advisories left outstanding — 1 advisory-carrying package(s) unaddressed past 90 days; oldest published 189 days ago
Inputs used
sourceosv
advisories8
affected_packages4
assessed_packages105
unassessed_packages5
affected_by_severityhigh 4
direct_affected_packages1
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories. Remaining weights renormalized. Matched 105 resolved dependencies against OSV. 5 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.

56Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://statamic.com/llms.txt)
35.7/40Legible commit history — 63 of 94 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://statamic.com/llms.txt
legible_history_share0.67
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environment — lockfile
10/10Demonstrated agent practice — 32 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 6 of the last 100 commits are automated dependency updates
10/10OpenSSF Scorecard: Pinned-Dependencies — all dependencies are pinned
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0.32
toolchain_manifests—
dependency_bot_commit_share0.06
How it's scored
0/45Type-checkable code — PHP without a type-check config
55/55Manageable file sizes — 0/234 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes40,722
source_files_sampled234
oversized_source_files0

Key facts

73GitHub stars
36contributors
344commits, last 12 months
1days since last push
100releases
2bus factor
9open issues
npm, 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 ★ / 48 ⇿
0Stars
48Forks
96Releases

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.

010203040504822018-082022-082026-08
Major 5Minor 30Patch 54

Each point covers 8 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-09 02:26 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
1Code-ReviewFound 5/27 approved changesets -- score normalized to 1
10Contributorsproject has 14 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
0Licenselicense file not detected
10Maintained30 commit(s) and 10 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
10Pinned-Dependenciesall dependencies are pinned
7SASTSAST tool is not run on all commits -- score normalized to 7
0Security-Policysecurity policy file not detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
2Vulnerabilities8 existing vulnerabilities detected
Direct dependencies 7
RegistryPackageVersion constraintManifest
Packagiststatamic/cms^6.25composer.json
Packagistspatie/simple-excel^3.9composer.json
npm@tailwindcss/vite^4.2.4package.json
npmcross-env^7.0.2package.json
npmstriptags^3.2.0package.json
npmtailwindcss^4.2.4package.json
npmunderscore~1.12.1package.json
All dependencies 110

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

RegistryPackageVersionRelation
npm@tailwindcss/vite4.2.4direct
npmcross-env7.0.3direct
npmstriptags3.2.0direct
npmtailwindcss4.2.4direct
npmunderscore1.12.1direct
Packagistspatie/simple-excel—direct
Packagiststatamic/cms—direct
npm@babel/helper-string-parser7.27.1indirect
npm@babel/helper-validator-identifier7.28.5indirect
npm@babel/parser7.29.2indirect
npm@babel/types7.29.0indirect
npm@emnapi/core1.10.0indirect
npm@emnapi/runtime1.10.0indirect
npm@emnapi/wasi-threads1.2.1indirect
npm@jridgewell/gen-mapping0.3.13indirect
npm@jridgewell/remapping2.3.5indirect
npm@jridgewell/resolve-uri3.1.2indirect
npm@jridgewell/sourcemap-codec1.5.5indirect
npm@jridgewell/trace-mapping0.3.31indirect
npm@napi-rs/wasm-runtime1.1.4indirect
npm@oxc-project/types0.127.0indirect
npm@rolldown/binding-android-arm641.0.0-rc.17indirect
npm@rolldown/binding-darwin-arm641.0.0-rc.17indirect
npm@rolldown/binding-darwin-x641.0.0-rc.17indirect
npm@rolldown/binding-freebsd-x641.0.0-rc.17indirect
npm@rolldown/binding-linux-arm-gnueabihf1.0.0-rc.17indirect
npm@rolldown/binding-linux-arm64-gnu1.0.0-rc.17indirect
npm@rolldown/binding-linux-arm64-musl1.0.0-rc.17indirect
npm@rolldown/binding-linux-ppc64-gnu1.0.0-rc.17indirect
npm@rolldown/binding-linux-s390x-gnu1.0.0-rc.17indirect
npm@rolldown/binding-linux-x64-gnu1.0.0-rc.17indirect
npm@rolldown/binding-linux-x64-musl1.0.0-rc.17indirect
npm@rolldown/binding-openharmony-arm641.0.0-rc.17indirect
npm@rolldown/binding-wasm32-wasi1.0.0-rc.17indirect
npm@rolldown/binding-win32-arm64-msvc1.0.0-rc.17indirect
npm@rolldown/binding-win32-x64-msvc1.0.0-rc.17indirect
npm@rolldown/pluginutils1.0.0-rc.13indirect
npm@rolldown/pluginutils1.0.0-rc.17indirect
npm@statamic/cms0.0.0indirect
npm@tailwindcss/node4.2.4indirect
npm@tailwindcss/oxide4.2.4indirect
npm@tailwindcss/oxide-android-arm644.2.4indirect
npm@tailwindcss/oxide-darwin-arm644.2.4indirect
npm@tailwindcss/oxide-darwin-x644.2.4indirect
npm@tailwindcss/oxide-freebsd-x644.2.4indirect
npm@tailwindcss/oxide-linux-arm-gnueabihf4.2.4indirect
npm@tailwindcss/oxide-linux-arm64-gnu4.2.4indirect
npm@tailwindcss/oxide-linux-arm64-musl4.2.4indirect
npm@tailwindcss/oxide-linux-x64-gnu4.2.4indirect
npm@tailwindcss/oxide-linux-x64-musl4.2.4indirect
npm@tailwindcss/oxide-wasm32-wasi4.2.4indirect
npm@tailwindcss/oxide-win32-arm64-msvc4.2.4indirect
npm@tailwindcss/oxide-win32-x64-msvc4.2.4indirect
npm@tybys/wasm-util0.10.1indirect
npm@vitejs/plugin-vue6.0.6indirect
npm@vue/compiler-core3.5.33indirect
npm@vue/compiler-dom3.5.33indirect
npm@vue/compiler-sfc3.5.33indirect
npm@vue/compiler-ssr3.5.33indirect
npm@vue/reactivity3.5.33indirect
npm@vue/runtime-core3.5.33indirect
npm@vue/runtime-dom3.5.33indirect
npm@vue/server-renderer3.5.33indirect
npm@vue/shared3.5.33indirect
npmcross-spawn7.0.6indirect
npmcsstype3.2.3indirect
npmdetect-libc2.1.2indirect
npmenhanced-resolve5.21.0indirect
npmentities7.0.1indirect
npmestree-walker2.0.2indirect
npmfdir6.5.0indirect
npmfsevents2.3.3indirect
npmgraceful-fs4.2.11indirect
npmisexe2.0.0indirect
npmjiti2.6.1indirect
npmlaravel-vite-plugin3.1.0indirect
npmlightningcss1.32.0indirect
npmlightningcss-android-arm641.32.0indirect
npmlightningcss-darwin-arm641.32.0indirect
npmlightningcss-darwin-x641.32.0indirect
npmlightningcss-freebsd-x641.32.0indirect
npmlightningcss-linux-arm-gnueabihf1.32.0indirect
npmlightningcss-linux-arm64-gnu1.32.0indirect
npmlightningcss-linux-arm64-musl1.32.0indirect
npmlightningcss-linux-x64-gnu1.32.0indirect
npmlightningcss-linux-x64-musl1.32.0indirect
npmlightningcss-win32-arm64-msvc1.32.0indirect
npmlightningcss-win32-x64-msvc1.32.0indirect
npmmagic-string0.30.21indirect
npmnanoid3.3.11indirect
npmpath-key3.1.1indirect
npmpicocolors1.1.1indirect
npmpicomatch2.3.2indirect
npmpicomatch4.0.4indirect
npmpostcss8.5.12indirect
npmrolldown1.0.0-rc.17indirect
npmshebang-command2.0.0indirect
npmshebang-regex3.0.0indirect
npmsource-map-js1.2.1indirect
npmtapable2.3.3indirect
npmtinyglobby0.2.16indirect
npmtslib2.8.1indirect
npmvite8.0.10indirect
npmvite-plugin-full-reload1.2.0indirect
npmvue3.5.33indirect
npmwhich2.0.2indirect
Packagistlaravel/pint1.29.1indirect
Packagistorchestra/testbench—indirect
Packagistphpunit/phpunit—indirect
Packagistspatie/laravel-ray—indirect
Dependency advisories 4

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

PackageVersionRelationSeverityAdvisoriesFixed in
underscore1.12.1directhigh11.13.8
nanoid3.3.11indirecthigh35.1.16
postcss8.5.12indirecthigh28.5.23
vite8.0.10indirecthigh28.0.16

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.