Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-20 13:48 UTC

PHPOffice / PHPWord

A pure PHP library for reading and writing word processing documents

PHPCustom license★ 7,589 stars⑂ 2,729 forkssince May 2012View on GitHub ↗

PHPOffice/PHPWord holds a health index of 84 out of 100, placing it in the Excellent band. It scores highest on Community & Adoption (88/100) and lowest on AI Readiness (55/100). It was last updated 12 days ago. 2 contributors account for most of its recent work.

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

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

Ownership

PHPOfficeOrganization
658 followers9 public repossince Jun 2012

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

Package ecosystems

Metrics by category

Vitality

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

57Moderate · 21% of overall
How it's scored
28.8/36Push recency — last push 12 days ago
8.3/36Commit cadence — 12/52 weeks with commits
13.8/18Commit volume — 33 commits in the last year
10/10OpenSSF Scorecard: Maintained — 26 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year33
human_commit_share0.94
days_since_last_push12
active_weeks_last_year12
How it's scored
27/27Ships releases — 26 releases published
7.2/36Release recency — latest release 502 days ago
12.6/27Release cadence — a release every ~174.8 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count26
latest_release_tag1.4.0
releases_from_tagsno
days_since_latest_release502
mean_days_between_releases174.8
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?

88Excellent · 17% of overall
How it's scored
60/60Stars — 7,589 stars
25/25Forks — 2,729 forks
13.8/15Watchers — 300 watchers
Inputs used
forks2,729
stars7,589
watchers300
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
16.9/22.5License — license file present, not a recognized license
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges5
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicescoveralls.io, github.com, poser.pugx.org
has_pull_request_templateyes
How it's scored
80/80Monthly downloads — 2,680,403 downloads/month across packagist
15.8/20Registry dependents — 236 packages depend on it
Inputs used
packagesphpoffice/phpword
dependents236
ecosystemspackagist
total_downloads46,988,018
monthly_downloads2,680,403
unverified_packages_excluded—

Sustainability & Governance

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

67Good · 23% of overall
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
15.7/22.5Commit distribution — top contributor authored 30% of commits
13.5/13.5Contributor breadth — 99 contributors
10/10OpenSSF Scorecard: Contributors — project has 21 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled99
top_contributor_share0.304
How it's scored
17.7/42Issue resolution — 42% of issues closed
17.4/30PR acceptance — 535/922 decided PRs merged
9.8/13Newcomer PR acceptance — 9/12 first-time contributors' PRs merged in 30d
13.5/15OpenSSF Scorecard: Code-Review — Found 29/30 approved changesets -- score normalized to 9
Inputs used
merged_prs535
open_issues1,086
closed_issues789
prs_merged_7d0
prs_decided_7d0
prs_merged_30d10
prs_decided_30d14
issue_closed_ratio0.421
closed_unmerged_prs387
first_time_authors_30d6
first_time_prs_merged_30d9
first_time_prs_decided_30d12
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
20.3/25Owner reach — 658 followers of PHPOffice
19.3/25Track record — 9 public repos, account ~14 yr old
Inputs used
followers658
owner_typeOrganization
is_verifiedno
owner_loginPHPOffice
public_repos9
account_age_days5,244
How it's scored
25/25Published & resolvable — 1 package(s) on packagist
14/35Publish recency — latest publish 502 days ago
20/20Version history — 26 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesphpoffice/phpword
ecosystemspackagist
any_deprecatedno
min_days_since_publish502

Engineering Quality

Are baseline engineering and documentation practices in place?

85Excellent · 19% of overall
How it's scored
24/24CI workflows — 2 workflow(s)
24/24Tests present
16/16Linter config — .php-cs-fixer.dist.php
0/9.6Pre-commit hooks
0/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_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://phpoffice.github.io/PHPWord/
10/10Repository description
10/10Topics — 10 topics
0/10Wiki
Inputs used
topicsphp, libreoffice-writer, msword, doc, docx, html, odt, pdf, rtf, office
has_wikino
homepagehttps://phpoffice.github.io/PHPWord/
docs_sitehttps://phpoffice.github.io/PHPWord/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

62Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — branch protection not enabled on development/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
6.8/7.5Code-Review — Found 29/30 approved changesets -- score normalized to 9
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.2/2.5License — license file detected
7.5/7.5Maintained — 26 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
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_aggregate6.2
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.

55Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 92 of 94 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.979
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — .php-cs-fixer.dist.php
0/11Static type checking
0/10Reproducible environment
4/10Demonstrated agent practice — 2 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 6 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.02
toolchain_manifests—
dependency_bot_commit_share0.06
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
54.5/55Manageable file sizes — 5/594 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes214,314
source_files_sampled594
oversized_source_files5
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
0/20MCP server — not applicable to this kind of software
40/40Runnable examples — samples
Inputs used
example_dirssamples
has_mcp_signalno
api_schema_files—
interfaces_expected_of—
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto), MCP server. Remaining weights renormalized.

Key facts

7,589GitHub stars
99contributors
33commits, last 12 months
12days since last push
26releases
2bus factor
1,086open 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 ★ / 2,729 ⇿
0Stars
2,729Forks
10Releases

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.

Only the most recent history is shown — this repository exceeds the collection window, so the earliest history is not captured.

1,5001,7502,0002,2502,5002,7502,729102020-042023-072026-10
Major 1Minor 5Patch 3

Each point covers 6 days.

OpenSSF Scorecard 6.2 / 10
6.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 13:48 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/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
9Code-ReviewFound 29/30 approved changesets -- score normalized to 9
10Contributorsproject has 21 contributing companies or organizations
n/aDangerous-Workflowno workflows found
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
10Maintained26 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
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
All dependencies 18

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

RegistryPackageVersionRelation
Packagistdompdf/dompdf—indirect
Packagistext-dom—indirect
Packagistext-json—indirect
Packagistext-libxml—indirect
Packagistext-xml—indirect
Packagistext-zip—indirect
Packagistfriendsofphp/php-cs-fixer—indirect
Packagistmpdf/mpdf—indirect
Packagistphp—indirect
Packagistphpmd/phpmd—indirect
Packagistphpoffice/common—indirect
Packagistphpoffice/math—indirect
Packagistphpoffice/wmf—indirect
Packagistphpstan/phpstan—indirect
Packagistphpstan/phpstan-phpunit—indirect
Packagistphpunit/phpunit—indirect
Packagistsymfony/process—indirect
Packagisttecnickcom/tcpdf—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.